debug_continue

THE RISK

High Risk

Why debug_continue needs a policy

This tool resumes execution on an embedded debug target via GDB. It triggers an external operation (resuming firmware execution on hardware) whose effects depend on the current state of the target. This is an Execute-category action — it causes real-world code to run on embedded hardware, which could have unpredictable side effects depending on the firmware being debugged.

From the tool's definition Continue target execution (asynchronous — returns immediately). GDB stays responsive after this.

Documented attack patterns abuse exactly the kind of access debug_continue gives an agent:

POLICY

How to control debug_continue

PolicyLayer is an MCP gateway — it sits between your AI agents and Openocd, and nothing reaches the server without passing your rules. This is the rule we recommend for debug_continue:

policy.json

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

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

Create a free account and register Openocd — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Openocd tools

Destructive shutdown Gracefully shut down the MCP server. Stops debug session if active, then exits. Execute debug_command Execute one GDB command in current active debug session. Execute debug_start Start debug session using specified launch configuration. Execute debug_stop Stop current active debug session and terminate OpenOCD/GDB processes. Execute debug_interrupt Interrupt/pause the running target via GDB/MI -exec-interrupt with platform-specific fallb Execute flash_download Flash firmware once using specified launch configuration without starting debug session. Execute debug_attach Attach to a running target without resetting or downloading firmware. Uses launch.json con Write set_project Set current project directory and load debug configurations from .vscode/launch.json.

All 14 Openocd tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Openocd → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about debug_continue

What does the debug_continue tool do? +

Continue target execution (asynchronous — returns immediately). GDB stays responsive after this. It is categorised as a Execute tool in the Openocd 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_continue? +

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

What risk level is debug_continue? +

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

Can I rate-limit debug_continue? +

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

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

debug_continue is provided by the Openocd MCP server (luiox/openocd-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Openocd tool call.

Start from Openocd, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →