Switch active tab by index
AI agents invoke switch_tab to trigger actions in Chrome Profile MCP Server. 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.
Switching the active tab is a browser action that changes the state of a running Chrome instance. It is part of a broader set of browser control tools and can be used to redirect agent focus to sensitive tabs, enabling follow-on actions like data extraction or interaction with authenticated sessions. It is not purely a read operation as it modifies browser UI state.
From the tool's definition Switch active tab by index — triggers a browser state change by switching the active tab in a live Chrome instance controlled via Chrome DevTools Protocol
Attacks that exploit this kind of access
Switch active tab by index. It is categorised as a Execute tool in the Chrome Profile MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Chrome Profile MCP Server MCP server in PolicyLayer and add a rule for switch_tab: 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 Chrome Profile MCP Server. Nothing to install.
switch_tab 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 switch_tab 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 switch_tab. 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.
switch_tab is provided by the Chrome Profile MCP Server MCP server (nghiahsgs/vibe-mcp-chrome). 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 →