High-risk tools in Debugger MCP Server
10 of the 41 tools in Debugger MCP Server 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
-
evaluate-expressionExecuteEvaluate JavaScript expressions in the context of a call frame
-
force-garbage-collectionExecuteForce garbage collection to free memory and analyze memory leaks
-
manage-breakpointsExecuteSet, remove, list, and manage breakpoints for debugging
-
modify-variableExecuteModify variable values in a specific scope
-
set-network-throttlingExecuteConfigure network throttling to simulate different connection speeds
-
start-cpu-profilingExecuteStart CPU profiling to analyze performance bottlenecks and generate flame graphs
-
start-heap-samplingExecuteStart heap sampling for memory profiling and leak detection
-
start-render-trackingExecuteStart tracking render performance for a specific component
-
stop-cpu-profilingExecuteStop CPU profiling and get the profile data with flame graph
-
take-heap-snapshotExecuteTake a detailed heap snapshot using Chrome DevTools for memory analysis
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.