debug_state

THE RISK

Low Risk

Why debug_state needs a policy

This tool only queries and returns the current state of a debug target without modifying, executing, or destructively affecting any system. It is informational only, analogous to checking a status flag. The lowest risk category (Read) applies.

From the tool's definition Tool name is 'debug_state' and description states it 'Get[s] target execution state (running/stopped) and last stop reason' — purely retrieves status information with no side effects.

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

POLICY

How to control debug_state

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_state:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "debug_state": {}
  }
}

debug_state is read-only, so it stays allowed — but 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.

CAP 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_continue Continue target execution (asynchronous — returns immediately). GDB stays responsive after 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

All 14 Openocd tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about debug_state

What does the debug_state tool do? +

Get target execution state (running/stopped) and last stop reason. It is categorised as a Read tool in the Openocd MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on debug_state? +

Register the Openocd MCP server in PolicyLayer and add a rule for debug_state: 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_state? +

debug_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit debug_state? +

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

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

debug_state 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 →