chrome_set_mode · Chrome MCP Stealth MCP: Risk & Policy

WHAT IT DOES

What chrome_set_mode does on Chrome MCP Stealth

AI agents invoke chrome_set_mode 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_set_mode needs a policy

This tool is part of a browser automation server and likely switches between operational modes (e.g., stealth/normal, headless/headful). It triggers a change in browser behavior/state, which qualifies as Execute. Severity is medium given the stealth automation context. Confidence is reduced because the description is cut off and does not fully explain what modes are being switched.

From the tool's definition Tool name 'chrome_set_mode' on a stealth browser automation server; description is truncated/uninformative ('Switch between')

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_set_mode Rate-limited

chrome_set_mode 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_set_mode": {
      "limits": [
        {
          "counter": "chrome_set_mode_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_set_mode

What does the chrome_set_mode tool do? +

Switch between. 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_set_mode? +

Register the Chrome MCP Stealth MCP server in PolicyLayer and add a rule for chrome_set_mode: 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_set_mode? +

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

Can I rate-limit chrome_set_mode? +

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

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

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