chrome_tabs · Chrome MCP Stealth MCP: Risk & Policy

WHAT IT DOES

What chrome_tabs does on Chrome MCP Stealth

AI agents invoke chrome_tabs to trigger actions in Chrome MCP Stealth. 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_tabs needs a policy

While listing tabs is a Read operation, the tool also creates and closes tabs, which constitute browser state mutations. Closing a tab could lose unsaved state irreversibly, and creating tabs triggers navigation/resource loading. The most severe applicable category for a tool that modifies browser state (create/close) is Execute.

From the tool's definition List/switch/create/close tabs — includes creating and closing tabs, which are active browser state-changing operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_tabs Rate-limited

chrome_tabs 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_tabs": {
      "limits": [
        {
          "counter": "chrome_tabs_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 Stealth, so you can run agents against it safely.

FAQ

Questions about chrome_tabs

What does the chrome_tabs tool do? +

List/switch/create/close tabs. It is categorised as a Execute tool in the Chrome MCP Stealth 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_tabs? +

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

What risk level is chrome_tabs? +

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

Can I rate-limit chrome_tabs? +

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

Set action: deny in the PolicyLayer policy for chrome_tabs. 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_tabs? +

chrome_tabs is provided by the Chrome MCP Stealth MCP server (riaan-fourie/chrome-mcp-stealth). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.