// MCP TOOL REFERENCE

CHROME DEBUG MCP SERVER TOOLS

3 tools from the Chrome Debug MCP Server MCP Server, categorised by risk level.

View the Chrome Debug MCP Server policy →
// ALL 3 CHROME DEBUG MCP SERVER TOOLS
READ 1 tools
Read get_console_logs Get console logs from Chrome
EXECUTE 2 tools
Execute evaluate Evaluate JavaScript in Chrome Execute launch_chrome Launch Chrome in debug mode

Route Chrome Debug MCP Server through PolicyLayer and every one of its 3 tools is checked against your policy before it runs.

GOVERN CHROME DEBUG →

Enforced before the call runs. Nothing to install.

// FAQ
How many tools does the Chrome Debug MCP Server MCP server have? +

The Chrome Debug MCP Server MCP server exposes 3 tools across 2 categories: Read, Execute.

How do I enforce policies on Chrome Debug MCP Server tools? +

Route the Chrome Debug MCP Server 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 Debug MCP Server tools fall into? +

Chrome Debug MCP Server tools are categorised as Read (1), Execute (2). Each category has a recommended default policy.

Enforce policy on every Chrome Debug MCP Server tool call.

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

GOVERN CHROME DEBUG →

Free to start. No card required.

42,500+ MCP servers and 110,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.