// MCP TOOL REFERENCE

MCP DEBUGGER NODE TOOLS

11 tools from the Mcp Debugger Node MCP Server, categorised by risk level.

// ALL 11 MCP DEBUGGER NODE TOOLS

READ 1 tools

Read get_variables Get variables for the latest paused call frame scope.

EXECUTE 10 tools

Execute reset Restart the debug session with a fresh Node inspector process for the provided target. Execute stop Stop the current debug target and clear the debug session. Execute wait_for_pause Wait until the debugged Node.js process pauses and return the current location. Execute continue Resume execution of the debugged Node.js process and return immediately. Execute evaluate Evaluate a JavaScript expression in the debugged runtime. Execute resume Resume execution of the debugged Node.js process and wait for the next pause. Execute set_breakpoint Set a breakpoint by matching a script URL with a regex. Execute set_pause_on_exceptions Configure whether the debugger pauses on no exceptions, uncaught exceptions, or all exceptions. Execute step_into Step into the next function call. Execute step_over Step over the current statement.

// FAQ

How many tools does the Mcp Debugger Node MCP server have? +

The Mcp Debugger Node MCP server exposes 11 tools across 2 categories: Read, Execute.

How do I enforce policies on Mcp Debugger Node tools? +

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

Mcp Debugger Node tools are categorised as Read (1), Execute (10). Each category has a recommended default policy.

Enforce policy on every Mcp Debugger Node tool call.

Start from Mcp Debugger Node, 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.