run · gdb and rr Debugging MCP: Risk & Policy

WHAT IT DOES

What run does on gdb and rr Debugging

AI agents invoke run to trigger actions in gdb and rr Debugging. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run needs a policy

This tool directly executes code by launching the debugged program. While the blast radius depends on what program is loaded, the tool itself is a direct execution primitive that runs external processes. It is not merely inspecting state (Read), not reversibly modifying data (Write), and not permanently deleting data (Destructive).

From the tool's definition Tool name 'run' with description 'Start or restart the inferior. Blocks until it stops.' — 'inferior' is GDB terminology for the target program being debugged.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run Rate-limited

run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run": {
      "limits": [
        {
          "counter": "run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches gdb and rr Debugging, so you can run agents against it safely.

FAQ

Questions about run

What does the run tool do? +

Start or restart the inferior. Blocks until it stops. It is categorised as a Execute tool in the gdb and rr Debugging MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run? +

Register the gdb and rr Debugging MCP server in PolicyLayer and add a rule for run: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches gdb and rr Debugging. Nothing to install.

What risk level is run? +

run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run? +

Yes. Add a rate_limit block to the run rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block run completely? +

Set action: deny in the PolicyLayer policy for run. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides run? +

run is provided by the gdb and rr Debugging MCP server (schuay/gdb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.