exec_command · gdb and rr Debugging MCP: Risk & Policy

WHAT IT DOES

What exec_command does on gdb and rr Debugging

AI agents invoke exec_command 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 exec_command needs a policy

This tool allows execution of arbitrary GDB commands, which can be leveraged to run, modify, or inspect programs in ways that depend entirely on the arguments provided. While GDB itself is a legitimate debugger, exposing unrestricted command execution to an AI agent creates significant risk of unintended code execution, unauthorized access to program state, or triggering malicious payloads embedded in debugged…

From the tool's definition Tool name 'exec_command' combined with description 'Execute any GDB command and return its output' indicates arbitrary command execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

exec_command Rate-limited

exec_command 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": {
    "exec_command": {
      "limits": [
        {
          "counter": "exec_command_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 exec_command

What does the exec_command tool do? +

Execute any GDB command and return its output. 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 exec_command? +

Register the gdb and rr Debugging MCP server in PolicyLayer and add a rule for exec_command: 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 exec_command? +

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

Can I rate-limit exec_command? +

Yes. Add a rate_limit block to the exec_command 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 exec_command completely? +

Set action: deny in the PolicyLayer policy for exec_command. 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 exec_command? +

exec_command 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.