High Risk →

switch_tab

Switch to the tab with the specified page ID. Args: page_id (int): The ID of the page to switch to Returns: str: A message confirming the tab switch

How to control switch_tab ↓

AI agents invoke switch_tab to trigger actions in Mcp Browser Use. 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

Switching tabs is a browser navigation action that changes the active context/state in the browser. It doesn't read, write, or destroy data on its own, but it executes a browser operation that can affect subsequent actions. The blast radius is low since it only changes focus between already-open tabs.

From the tool's definition Switch to the tab with the specified page ID — triggers a browser action (tab switching) that changes the active browser context

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

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

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

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 Mcp Browser Use — 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 switch_tab tool do? +

Switch to the tab with the specified page ID. Args: page_id (int): The ID of the page to switch to Returns: str: A message confirming the tab switch. It is categorised as a Execute tool in the Mcp Browser Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on switch_tab? +

Register the Mcp Browser Use 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 Mcp Browser Use. Nothing to install.

What risk level is switch_tab? +

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

Can I rate-limit switch_tab? +

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.

How do I block switch_tab completely? +

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.

What MCP server provides switch_tab? +

switch_tab is provided by the Mcp Browser Use MCP server (vinayak-mehta/mcp-browser-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Browser Use tool call.

Deterministic rules across all 19 Mcp Browser Use tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

19 Mcp Browser Use 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.