// MCP TOOL REFERENCE

MCP NODEJS DEBUGGER TOOLS

13 tools from the MCP NodeJS Debugger MCP Server, categorised by risk level.

// ALL 13 MCP NODEJS DEBUGGER TOOLS

READ 4 tools

Read get_console_output Gets the most recent console output from the debugged process Read get_location Gets the current execution location when paused Read inspect_variables Inspects variables in current scope Read list_breakpoints Lists all active breakpoints

DESTRUCTIVE 1 tools

Destructive delete_breakpoint Deletes a specified breakpoint

EXECUTE 8 tools

Execute continue Continues code execution Execute evaluate Evaluates a JavaScript expression in the current context Execute nodejs_inspect Executes JavaScript code in the debugged process Execute step_into Steps into function calls Execute step_out Steps out of current function Execute step_over Steps over to the next line of code Execute retry_connect Manually triggers a reconnection attempt to the Node.js debugger Execute set_breakpoint Sets a breakpoint at specified line and file

// FAQ

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

The MCP NodeJS Debugger MCP server exposes 13 tools across 3 categories: Read, Destructive, Execute.

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

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

MCP NodeJS Debugger tools are categorised as Read (4), Destructive (1), Execute (8). Each category has a recommended default policy.

Enforce policy on every MCP NodeJS Debugger tool call.

Deterministic rules across all 13 MCP NodeJS Debugger tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN MCP NODEJS DEBUGGER →

Free to start. No card required.

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