High-risk tools in Mcp Debugpy
10 of the 16 tools in Mcp Debugpy 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
-
dap_continueExecuteContinue execution on the specified (or last stopped) thread.
-
dap_launchExecutedap_launch
-
dap_shutdownExecuteTerminate the current DAP adapter session.
-
dap_step_inExecuteStep into the next function call on the active thread.
-
dap_step_outExecuteStep out of the current function on the active thread.
-
dap_step_overExecuteStep over the next line on the active thread.
-
dap_wait_for_eventExecuteWait for a specific DAP event (e.g., 'stopped').
-
run_tests_focusExecuteRun a focused subset: pytest -k <keyword> with JSON report.
-
run_tests_jsonExecuterun_tests_json
-
dap_set_breakpointsExecutedap_set_breakpoints
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.