print · gdb and rr Debugging MCP: Risk & Policy

WHAT IT DOES

What print does on gdb and rr Debugging

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

While called 'print', this tool executes arbitrary GDB expressions that can have side effects (invoking getters, calling functions, modifying memory if combined with other GDB features). The severity is high because a compromised AI could use expression evaluation to exfiltrate sensitive data, trigger unintended function calls, or inspect protected memory regions during debugging sessions.

From the tool's definition Tool evaluates GDB expressions via 'print' command, which executes arbitrary code evaluation within a debugged process context. GDB's print command can trigger function calls, execute complex expressions, and interact with process memory and state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

print Rate-limited

print 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": {
    "print": {
      "limits": [
        {
          "counter": "print_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 print

What does the print tool do? +

Evaluate a GDB expression (print). 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 print? +

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

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

Can I rate-limit print? +

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

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

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