gdb_interrupt · GDB Lite MCP: Risk & Policy

WHAT IT DOES

What gdb_interrupt does on GDB Lite MCP

AI agents invoke gdb_interrupt to trigger actions in GDB Lite MCP. 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 gdb_interrupt needs a policy

This tool sends a SIGINT signal to a running GDB session or its debuggee process, which is an external operation that interrupts execution. It triggers a signal delivery to a process, which qualifies as Execute. The blast radius is medium — it can interrupt a running program but is generally recoverable (the session continues in GDB).

From the tool's definition Send SIGINT to the gdb session/debuggee, wait for the GDB prompt, and return incremental output.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gdb_interrupt Rate-limited

gdb_interrupt 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": {
    "gdb_interrupt": {
      "limits": [
        {
          "counter": "gdb_interrupt_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 Lite MCP, so you can run agents against it safely.

FAQ

Questions about gdb_interrupt

What does the gdb_interrupt tool do? +

Send SIGINT to the gdb session/debuggee, wait for the GDB prompt, and return incremental output. It is categorised as a Execute tool in the GDB Lite MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on gdb_interrupt? +

Register the GDB Lite MCP server in PolicyLayer and add a rule for gdb_interrupt: 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 Lite MCP. Nothing to install.

What risk level is gdb_interrupt? +

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

Can I rate-limit gdb_interrupt? +

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

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

gdb_interrupt is provided by the GDB Lite MCP server (mort2000/gdb-lite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

gdb_interrupt is one line of GDB Lite's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →