browser.launch_chrome_cdp · MCP Playwright Browser MCP

WHAT IT DOES

What browser.launch_chrome_cdp does on MCP Playwright Browser

AI agents invoke browser.launch_chrome_cdp to trigger actions in MCP Playwright Browser. 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 browser.launch_chrome_cdp needs a policy

This tool launches a Chrome browser process with remote debugging (CDP) enabled, which creates a controllable browser instance that can be directed to perform arbitrary web operations. This is an Execute-category action because it initiates an external process (Chrome) and establishes a debugging connection that can be used to run arbitrary browser automation.

From the tool's definition Launch Chrome with remote debugging enabled and connect via CDP

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser.launch_chrome_cdp Rate-limited

browser.launch_chrome_cdp 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": {
    "browser.launch_chrome_cdp": {
      "limits": [
        {
          "counter": "browser.launch_chrome_cdp_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 MCP Playwright Browser, so you can run agents against it safely.

FAQ

Questions about browser.launch_chrome_cdp

What does the browser.launch_chrome_cdp tool do? +

Launch Chrome with remote debugging enabled and connect via CDP. It is categorised as a Execute tool in the MCP Playwright Browser MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser.launch_chrome_cdp? +

Register the MCP Playwright Browser MCP server in PolicyLayer and add a rule for browser.launch_chrome_cdp: 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 MCP Playwright Browser. Nothing to install.

What risk level is browser.launch_chrome_cdp? +

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

Can I rate-limit browser.launch_chrome_cdp? +

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

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

browser.launch_chrome_cdp is provided by the MCP Playwright Browser MCP server (mhrnqaruni/mcp-playwright-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.