// MCP TOOL REFERENCE

CHROME DEBUGGER MCP TOOLS

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

READ TOOLS

getScopeVariables [STEP 6a] Read all scope variables (local, closure, module) at the currently paused call frame. Call this immediately after waitForSpecificPause ... getStatus Non-blocking: return current connection and pause state immediately without waiting. Use this to poll for pause instead of waitForPause when the ... listTargets [STEP 2] List all open Chrome tabs available for debugging. MANDATORY: show the full list to the user and ask "Which URL do you want to debug?" NEV...

WRITE TOOLS

connect [STEP 3] Connect the debugger to a specific Chrome tab. MANDATORY: call listTargets first, show the list to the user, wait for their explicit URL c... 2/5 disconnect Disconnect the current Chrome debugging session and clear in-memory pause state. Use this to explicitly end a debug session before connecting again. 2/5 resume [STEP 8] Resume script execution after collecting all needed variable data — ends the current pause. After calling resume, remove all temporary d... 2/5 setBreakpoint Set a breakpoint at a specific script URL and line number via CDP — no source code modification needed. Use a full URL (https://...) for exact ma... 2/5

DESTRUCTIVE TOOLS

forcePause Force the debugger to pause at the very next JavaScript statement. Useful when you cannot modify source code to add debugger; and setBreakpoint is ... 4/5 removeBreakpoint Remove a previously set CDP breakpoint by its ID (returned by setBreakpoint). 4/5

EXECUTE TOOLS

evaluate [STEP 6b] Evaluate any JavaScript expression in the context of the currently paused call frame. Use this to inspect nested objects, call methods,... 3/5 launchChrome [STEP 1] Launch a dedicated Chrome instance with remote debugging enabled (default port 9222). Uses --user-data-dir=~/.chrome-debug-profile so your... 4/5 reloadPage [STEP 5a] Reload the connected page via Chrome DevTools Protocol. More reliable than manual browser refresh — maintains the CDP connection and en... 3/5 startDebuggingSession CALL THIS FIRST whenever browser-side debugging is needed — before any other tool. Auto-trigger when user mentions any of: debug, breakpoint, de... 3/5 stepInto [STEP 7] BLOCKING: step into the next function call, then wait until the debugger pauses again. Follow with getScopeVariables() to observe inner-fu... 3/5 stepOut [STEP 7] BLOCKING: step out of the current function and wait until the debugger pauses again in the caller. Use to observe the return value and the... 3/5 stepOver [STEP 7] BLOCKING: step over the current statement without entering function calls, then wait until the debugger pauses again. Follow with getScope... 3/5 waitForPause [STEP 5b — FALLBACK] BLOCKING call — waits until ANY debugger pause occurs (breakpoint, debugger; statement, or exception). Before blocking, send... 3/5 waitForSpecificPause [STEP 5b — PREFERRED] BLOCKING call — waits for the next debugger pause, then checks if it matches the target location. ⚠️ NO AUTO-RESUME: exe... 3/5

// 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? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Chrome Debugger MCP 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.

Enforce policies on Chrome Debugger MCP

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →