chrome_switch_tab · Chrome MCP Server MCP: Risk & Policy

WHAT IT DOES

What chrome_switch_tab does on Chrome MCP Server

AI agents invoke chrome_switch_tab to trigger actions in Chrome 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.

WHY IT NEEDS A POLICY

Why chrome_switch_tab needs a policy

Switching the active tab is a browser control action that changes the browser's UI state and focus. While not destructive or financial, it is an external operation that affects the browser environment and could be used to redirect attention, expose sensitive tab content, or facilitate further automated actions. It falls under Execute as it triggers an external browser operation.

From the tool's definition "Switch the current active tab" — triggers a browser action that changes the active state of browser tabs

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_switch_tab Rate-limited

chrome_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "chrome_switch_tab": {
      "limits": [
        {
          "counter": "chrome_switch_tab_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Chrome MCP Server, so you can run agents against it safely.

FAQ

Questions about chrome_switch_tab

What does the chrome_switch_tab tool do? +

Switch the current active tab. It is categorised as a Execute tool in the Chrome MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on chrome_switch_tab? +

Register the Chrome MCP Server MCP server in PolicyLayer and add a rule for chrome_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 MCP Server. Nothing to install.

What risk level is chrome_switch_tab? +

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

Can I rate-limit chrome_switch_tab? +

Yes. Add a rate_limit block to the chrome_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 chrome_switch_tab completely? +

Set action: deny in the PolicyLayer policy for chrome_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 chrome_switch_tab? +

chrome_switch_tab is provided by the Chrome MCP Server MCP server (standbyme626/mcp-chrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.