Switch the current browser automation to a different tab by its ID. Get available tab IDs from browser_tabs tool. The switched tab becomes the active tab for subsequent browser operations. Returns: (1) shortened YAML snapshot text, (2) base64 PNG screenshot, (3) base64 PNG screenshot with refs of...
AI agents invoke browser_tab_switch to trigger actions in Search. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
tabId | number | Yes | The tab ID to switch to (from browser_tabs output) |
Parameters from the server's own tool schema.
This tool triggers an external browser operation (switching active tabs) that affects subsequent browser interactions. It's not purely reading data — it changes the state of the browser session. The blast radius is low since switching tabs itself causes no destructive or financial harm, but it is an action that modifies the operational context.
From the tool's definition Switch the current browser automation to a different tab by its ID... The switched tab becomes the active tab for subsequent browser operations
Attacks that exploit this kind of access
Switch the current browser automation to a different tab by its ID. Get available tab IDs from browser_tabs tool. The switched tab becomes the active tab for subsequent browser operations. Returns: (1) shortened YAML snapshot text, (2) base64 PNG screenshot, (3) base64 PNG screenshot with refs of the switched tab. Warning: Snapshot may not reflect latest page state due to async web content; call browser_snapshot to get current state if needed. It is categorised as a Execute tool in the Search MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browser_tab_switch accepts 1 parameter: tabId. Required: tabId. The full parameter table on this page comes from the server's own tool schema.
Register the Search MCP server in PolicyLayer and add a rule for browser_tab_switch: 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 Search. Nothing to install.
browser_tab_switch 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_tab_switch 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_tab_switch. 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_tab_switch is provided by the Search MCP server (search-mcp-server). 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 →