High-risk tools in gdb and rr Debugging

High severity gdb and rr Debugging MCP Server 13 of 15 tools

13 of the 15 tools in gdb and rr Debugging 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

batch_commands Execute

Execute GDB commands sequentially, returning each output.
breakpoint Execute

Set a breakpoint. Triggers in both directions in rr sessions.
continue_exec Execute

Continue execution. Blocks until next stop.
exec_command Execute

Execute any GDB command and return its output.
finish Execute

Run until current function returns. Blocks until stopped.
print Execute

Evaluate a GDB expression (print).
rr_record Execute

rr_record
run Execute

Start or restart the inferior. Blocks until it stops.
start_replay_session Execute

Start an rr replay session for time-travel debugging.
start_session Execute

Start a new GDB session. Returns session_id for all other tools.
step Execute

Step one source line or instruction. Blocks until stopped.
stop_session Execute

Stop and clean up a GDB session (kills the GDB process).
watch Execute

Set a watchpoint that stops when an expression changes.

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 gdb and rr Debugging

Tools at high risk

Attacks that target this class

More on gdb and rr Debugging

Enforce policy on every gdb and rr Debugging tool call.