// MCP TOOL REFERENCE

CHROME MCP DOCKER TOOLS

10 tools from the Chrome MCP Docker MCP Server, categorised by risk level.

// ALL 10 CHROME MCP DOCKER TOOLS

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.

WRITE 1 tools

Write type Types text into an input field.

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.

// FAQ

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

The Chrome MCP Docker MCP server exposes 10 tools across 3 categories: Read, Write, Execute.

How do I enforce policies on Chrome MCP Docker tools? +

Route the Chrome MCP Docker server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Chrome MCP Docker tools fall into? +

Chrome MCP Docker tools are categorised as Read (4), Write (1), Execute (5). Each category has a recommended default policy.

Enforce policy on every Chrome MCP Docker tool call.

Start from Chrome MCP Docker, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.