debug_pause · Polybugger MCP: Risk & Policy

WHAT IT DOES

What debug_pause does on Polybugger

AI agents invoke debug_pause to trigger actions in Polybugger. 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 debug_pause needs a policy

This tool sends a pause/interrupt signal to a running process, which is an external operation that affects program execution state. It's not purely reading data, nor does it delete anything, but it actively controls execution flow of a running program.

From the tool's definition Pause a running program

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debug_pause Rate-limited

debug_pause 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": {
    "debug_pause": {
      "limits": [
        {
          "counter": "debug_pause_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 Polybugger, so you can run agents against it safely.

FAQ

Questions about debug_pause

What does the debug_pause tool do? +

Pause a running program. It is categorised as a Execute tool in the Polybugger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on debug_pause? +

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

What risk level is debug_pause? +

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

Can I rate-limit debug_pause? +

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

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

debug_pause is provided by the Polybugger MCP server (wilfoa/polybugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.