chrome_console · Chrome MCP Server MCP: Risk & Policy

WHAT IT DOES

What chrome_console does on Chrome MCP Server

AI agents invoke chrome_console 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_console needs a policy

While the description says 'capture and retrieve', a console tool in a browser context typically allows executing JavaScript in the browser console and reading the output. The server description explicitly states AI can 'take control of your browser', and console access in browsers means JavaScript execution capability. Even if it only reads console output, it still exposes sensitive data from the browser session.

From the tool's definition Capture and retrieve console output from browser tabs

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_console Rate-limited

chrome_console 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_console": {
      "limits": [
        {
          "counter": "chrome_console_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_console

What does the chrome_console tool do? +

Capture and retrieve console output from browser tabs. 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_console? +

Register the Chrome MCP Server MCP server in PolicyLayer and add a rule for chrome_console: 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_console? +

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

Can I rate-limit chrome_console? +

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

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

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