Rehearsal Revealed Why Browser Agents Need Separate Identities
Original source
We Built An Agent That Broke All of Our Security Rules. Here's What We Learned.
The Hacker News →Token created Rehearsal, a browser agent that autonomously handles tasks within their platform by opening pages, adjusting filters, and completing forms. Because the agent runs within a user’s authenticated session, servers cannot distinguish its actions from the user’s—nothing in the session cookie reveals that an agent is driving the interaction. The application sees only the user, not the agent, the delegation, or the specific task scope.
Since Token owns both Rehearsal and its backend platform, the team implemented controls unavailable to third parties. They recorded all agent activity, reduced the agent’s access below the user’s level (read-only dashboards, blocked unsecured saves), visually indicated when the agent was in control, and interpreted sensitive fields through accessibility labels. Third-party agents deployed in real-world systems like CRMs or cloud platforms have none of these protections because external developers cannot modify the application to add them.
Several emerging standards attempt to address this gap. Chrome auto-browse requires user approval before high-stakes actions and restricts agents to necessary sites. WebMCP, a draft specification from Google and Microsoft, allows applications to publish their actions as tools so agents don’t guess what buttons do. Web Bot Auth, an IETF working group draft, enables sites to verify which agent made a request. Yet each standard solves only part of the problem. None reliably carry together the three signals applications need: the agent’s identity, proof that a specific human authorized it, and access limited to the task’s scope. Until standards align around these three elements, security teams must immediately catalog agentic browsers and extensions, implement step-up authentication for sensitive operations, and track which humans and agents access their systems.
Read the full article
Continue reading at The Hacker News →This is an AI-generated summary. Read the original for the full story.