// MCP TOOL REFERENCE

CHROME DEBUGGER MCP TOOLS

18 tools from the Chrome Debugger MCP MCP Server, categorised by risk level.

// ALL 18 CHROME DEBUGGER MCP TOOLS

READ 3 tools

Read getScopeVariables [STEP 6a] Read all scope variables (local, closure, module) at the currently paused call frame. Call this... Read getStatus Non-blocking: return current connection and pause state immediately without waiting. Use this to poll for... Read listTargets [STEP 2] List all open Chrome tabs available for debugging. MANDATORY: show the full list to the user and a...

WRITE 4 tools

Write connect [STEP 3] Connect the debugger to a specific Chrome tab. MANDATORY: call listTargets first, show the list to... Write disconnect Disconnect the current Chrome debugging session and clear in-memory pause state. Use this to explicitly end... Write resume [STEP 8] Resume script execution after collecting all needed variable data — ends the current pause. Afte... Write setBreakpoint Set a breakpoint at a specific script URL and line number via CDP — no source code modification needed. U...

DESTRUCTIVE 2 tools

Destructive forcePause Force the debugger to pause at the very next JavaScript statement. Useful when you cannot modify source cod... Destructive removeBreakpoint Remove a previously set CDP breakpoint by its ID (returned by setBreakpoint).

EXECUTE 9 tools

Execute evaluate [STEP 6b] Evaluate any JavaScript expression in the context of the currently paused call frame. Use this ... Execute launchChrome [STEP 1] Launch a dedicated Chrome instance with remote debugging enabled (default port 9222). Uses --user-... Execute reloadPage [STEP 5a] Reload the connected page via Chrome DevTools Protocol. More reliable than manual browser refre... Execute startDebuggingSession CALL THIS FIRST whenever browser-side debugging is needed — before any other tool. Auto-trigger when user ... Execute stepInto [STEP 7] BLOCKING: step into the next function call, then wait until the debugger pauses again. Follow with... Execute stepOut [STEP 7] BLOCKING: step out of the current function and wait until the debugger pauses again in the caller.... Execute stepOver [STEP 7] BLOCKING: step over the current statement without entering function calls, then wait until the deb... Execute waitForPause [STEP 5b — FALLBACK] BLOCKING call — waits until ANY debugger pause occurs (breakpoint, debugger; statement... Execute waitForSpecificPause [STEP 5b — PREFERRED] BLOCKING call — waits for the next debugger pause, then checks if it matches the targ...

// RUNNING THIS SERVER

The managed route: connect Chrome Debugger MCP through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y chrome-debugger-mcp

// FAQ

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

The Chrome Debugger MCP MCP server exposes 18 tools across 4 categories: Read, Write, Destructive, Execute.

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

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

Chrome Debugger MCP tools are categorised as Read (3), Write (4), Destructive (2), Execute (9). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.