High-risk tools in Mcp Debugger Node
10 of the 11 tools in Mcp Debugger Node 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
-
resetExecuteRestart the debug session with a fresh Node inspector process for the provided target.
-
stopExecuteStop the current debug target and clear the debug session.
-
wait_for_pauseExecuteWait until the debugged Node.js process pauses and return the current location.
-
continueExecuteResume execution of the debugged Node.js process and return immediately.
-
evaluateExecuteEvaluate a JavaScript expression in the debugged runtime.
-
resumeExecuteResume execution of the debugged Node.js process and wait for the next pause.
-
set_breakpointExecuteSet a breakpoint by matching a script URL with a regex.
-
set_pause_on_exceptionsExecuteConfigure whether the debugger pauses on no exceptions, uncaught exceptions, or all exceptions.
-
step_intoExecuteStep into the next function call.
-
step_overExecuteStep over the current statement.
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.