AI agents invoke browser_open_account_home to trigger actions in Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool opens a browser session using authenticated credentials and keeps the session alive for further interactions. It triggers an external browser operation and establishes a persistent session, which is characteristic of Execute category — it initiates a stateful browser session that enables follow-up actions, going beyond a simple read.
From the tool's definition Open the authenticated account home page in a new browser session and keep the session alive for follow-up actions.
Attacks that exploit this kind of access
Open the authenticated account home page in a new browser session and keep the session alive for follow-up actions. It is categorised as a Execute tool in the Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP server in PolicyLayer and add a rule for browser_open_account_home: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp. Nothing to install.
browser_open_account_home is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the browser_open_account_home rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for browser_open_account_home. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
browser_open_account_home is provided by the MCP server (victormyschik/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →