High-risk tools in Mcp Debugger
11 of the 22 tools in Mcp 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
-
attach_to_processExecuteAttach to a running process for debugging
-
continue_executionExecuteContinue execution
-
create_debug_sessionExecuteCreate a new debugging session. Provide host and port to attach to a running process; omit them for launch mode
-
detach_from_processExecuteDetach from the debugged process without terminating it
-
evaluate_expressionExecuteEvaluate expression in the current debug context. Expressions can read and modify program state
-
pause_executionExecutePause a running program
-
redefine_classesExecuteHot-swap changed Java classes into a running JVM. Scans a classes directory for .class files modified after sinceTimestamp, matches them against loaded classes in the target JVM...
-
start_debuggingExecuteStart debugging a script
-
step_intoExecuteStep into
-
step_outExecuteStep out
-
step_overExecuteStep over
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.