Emerging Agentic Features in Browsers: A Double-Edged Sword
As technology evolves, an increasing number of browsers are experimenting with agentic features designed to perform tasks on behalf of users, such as booking tickets or shopping for various items. However, these new capabilities come with inherent security risks, potentially leading to data loss or financial theft.
Google’s Approach to Security in Chrome
In recent announcements, Google has detailed its strategy for handling user security on Chrome, particularly concerning these agentic capabilities. During a preview in September, the company assured that these features would soon be rolled out, emphasizing a commitment to user safety.
To manage agentic actions effectively, Google has implemented several models. One such model is the User Alignment Critic, built using their Gemini technology. This component is designed to evaluate action items proposed by a planning model for specific tasks. If the critic model determines that the proposed tasks do not align with the user’s goals, it prompts the planner model to reassess its strategy. Importantly, this critic model accesses only the metadata of proposed actions, ensuring user privacy by not viewing the actual web content.
Image Credits: Google
Maintaining Security Through Constraints
To further mitigate risks, Google has introduced the concept of Agent Origin Sets, restricting the model’s access to designated read-only and read-writeable origins. For instance, within a shopping site, the agent is allowed to consume relevant listings but restricted from engaging with unrelated banner ads. This cautious approach ensures that data accessed by the agent is confined to a limited set of origins, effectively reducing the threat vector of cross-origin data leaks. The browser can enforce this separation by refraining from sending data outside the designated readable set to the model.
Additionally, Google employs another observer model to monitor page navigation, which serves to block any harmful URLs generated by the agent’s actions.

User Control Over Sensitive Actions
In a remarkable move, Google is transferring the control back to users for sensitive operations. For example, when an agent attempts to access websites that may contain sensitive information—like banking or medical data—it first seeks the user’s approval. For sites requiring login, the agent will request permission to utilize the password manager. Google assures that the agent’s model doesn’t have direct access to password data. Furthermore, users will be prompted before the agent undertakes actions such as making purchases or sending messages, ensuring comprehensive user consent.
Additionally, Google is active in testing its agentic capabilities to ward off potential threats. A prompt-injection classifier is in place to help prevent unwanted actions, and the company is examining these features against attacks devised by security researchers.
Google’s advancements in browser security signal an overarching trend, as streaming platforms continue to pay attention to potential risks. Earlier this month, Perplexity, another tech company, launched an open-source content detection model aimed at counteracting prompt injection attacks against agent features.
For further information, you can read the full article Here.
Image Credit: techcrunch.com






