High-risk tools in MCP NodeJS Debugger

High severity MCP NodeJS Debugger MCP Server 8 of 13 tools

8 of the 13 tools in MCP NodeJS Debugger are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.

Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.

Tools at high risk

continue Execute

Continues code execution
evaluate Execute

Evaluates a JavaScript expression in the current context
nodejs_inspect Execute

Executes JavaScript code in the debugged process
step_into Execute

Steps into function calls
step_out Execute

Steps out of current function
step_over Execute

Steps over to the next line of code
retry_connect Execute

Manually triggers a reconnection attempt to the Node.js debugger
set_breakpoint Execute

Sets a breakpoint at specified line and file

Attacks that target this class

High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.

Destructive Action Autonomy
Runaway Tool Loops
Prompt Injection via Tool Results

High-risk tools in MCP NodeJS Debugger

Tools at high risk

Attacks that target this class

More on MCP NodeJS Debugger

Enforce policy on every MCP NodeJS Debugger tool call.