High Risk →

browser_switch_tab

Switch the active MCP browser tab without changing the visible Chrome tab. Args: tab_id: The tab ID to switch to (from browser_get_tabs).

How to control browser_switch_tab ↓

AI agents invoke browser_switch_tab to trigger actions in Cdp Bridge. 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.

High Risk

This tool triggers an external operation in the browser session — switching the active MCP tab context. It affects the state of an ongoing browser automation session and determines which tab subsequent browser operations target, which can have cascading effects. It does not merely read data, but changes the active context/state of the browser automation environment.

From the tool's definition Switch the active MCP browser tab without changing the visible Chrome tab

Documented attack patterns abuse exactly the kind of access browser_switch_tab gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Cdp Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_switch_tab:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_switch_tab": {
      "limits": [
        {
          "counter": "browser_switch_tab_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

browser_switch_tab stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Cdp Bridge — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the browser_switch_tab tool do? +

Switch the active MCP browser tab without changing the visible Chrome tab. Args: tab_id: The tab ID to switch to (from browser_get_tabs). It is categorised as a Execute tool in the Cdp Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_switch_tab? +

Register the Cdp Bridge MCP server in PolicyLayer and add a rule for browser_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 Cdp Bridge. Nothing to install.

What risk level is browser_switch_tab? +

browser_switch_tab is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_switch_tab? +

Yes. Add a rate_limit block to the browser_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.

How do I block browser_switch_tab completely? +

Set action: deny in the PolicyLayer policy for browser_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.

What MCP server provides browser_switch_tab? +

browser_switch_tab is provided by the Cdp Bridge MCP server (unagi-cq/cdp-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cdp Bridge tool call.

Deterministic rules across all 9 Cdp Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

9 Cdp Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.