connect_remote_chrome · Chrome DevTools MCP Server MCP

WHAT IT DOES

What connect_remote_chrome does on Chrome DevTools MCP Server

AI agents use connect_remote_chrome to create or update resources in Chrome DevTools MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chrome DevTools MCP Server environment.

WHY IT NEEDS A POLICY

Why connect_remote_chrome needs a policy

An AI agent can call connect_remote_chrome faster than any human can review — one bad instruction and it creates or modifies resources in Chrome DevTools MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_remote_chrome Rate-limited

connect_remote_chrome stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect_remote_chrome": {
      "limits": [
        {
          "counter": "connect_remote_chrome_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 DevTools MCP Server, so you can run agents against it safely.

FAQ

Questions about connect_remote_chrome

What does the connect_remote_chrome tool do? +

Connect to a remote Chrome/Chromium instance (e.g., Electron app) via Chrome DevTools Protocol. Use this instead of launching a new Chrome when debugging an already running application. It is categorised as a Write tool in the Chrome DevTools MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on connect_remote_chrome? +

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

What risk level is connect_remote_chrome? +

connect_remote_chrome is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit connect_remote_chrome? +

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

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

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