// SCAN REPORT

Chrome MCP Docker

10 tools. 6 can modify or destroy data without limits.

6 write tools that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

6 can modify or destroy data

4 read-only

10 tools total

Community server · catalogue entry verified 12/06/2026

How to control Chrome MCP Docker ↓

TOOL MAP

What Chrome MCP Docker exposes to your agents

Read (4) Write / Execute (6) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Chrome MCP Docker tools

Execute · High navigate Navigation to arbitrary URLs causes the browser to fetch, parse, and execute code (JavaScript, etc.) on those remote pages. Execute · Medium wait_for_selector This tool executes a wait operation in a Chrome browser, making it Execute rather than Read. Execute · High click Clicking elements in a browser can trigger a wide range of side effects: form submissions, purchases, deletions, navigation, file downloads, etc. Execute · Low scroll Scrolling is a browser interaction/execution action that manipulates the browser state.

6 of Chrome MCP Docker's 10 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Chrome MCP Docker

PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome MCP Docker, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "type": {
    "limits": [
      {
        "counter": "type_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_computed_styles": {
    "limits": [
      {
        "counter": "get_computed_styles_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Chrome MCP Docker — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CHROME MCP DOCKER →

Free to start. No card required.

FULL CATALOGUE

All 10 Chrome MCP Docker tools

EXECUTE 5 tools

Execute navigate Navigates to a URL and waits for network idle. Execute wait_for_selector Waits for an element to appear in the DOM. Execute mobile_mode Toggles mobile viewport (iPhone X dimensions). Execute click Clicks an element identified by CSS selector. Execute scroll Scrolls the page. Use x,y coordinates OR selector to scroll into view.

WRITE 1 tools

Write type Types text into an input field.

READ 4 tools

Read get_computed_styles Returns the computed CSS styles for an element (essential for UI debugging). Read get_console_logs Returns captured console logs (errors, warnings, info). Useful for debugging JS issues. Read get_network_errors Returns a list of failed network requests. Read screenshot Takes a screenshot of the viewport. Returns base64.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Chrome MCP Docker

How do I prevent bulk modifications through Chrome MCP Docker? +

The Chrome MCP Docker server has 1 write tools including type. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Chrome MCP Docker.

How many tools does the Chrome MCP Docker MCP server expose? +

10 tools across 3 categories: Execute, Read, Write. 4 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Chrome MCP Docker? +

Register the Chrome MCP Docker MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Chrome MCP Docker tool call.

Deterministic rules across all 10 Chrome MCP Docker tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CHROME MCP DOCKER →

Free to start. No card required.

10 Chrome MCP Docker tools catalogued and risk-classified — across an index of 43,000+ MCP servers.