Get current debug session status in JSON format.
AI agents call debug_status to retrieve information from Openocd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports the current state of a debug session. It performs no writes, executions, deletions, or financial operations. The operation is read-only and non-destructive, making it the safest category. Even if an AI agent calls this repeatedly or in rapid succession, no harm results—it merely queries existing state.
From the tool's definition Tool name 'debug_status' and description 'Get current debug session status in JSON format' indicate a retrieval operation with no side effects. This is a query/monitoring function that returns status information without modifying any state.
Documented attack patterns abuse exactly the kind of access debug_status gives an agent:
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_status:
{
"version": "1",
"default": "deny",
"tools": {
"debug_status": {}
}
}debug_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get current debug session status in JSON format. It is categorised as a Read tool in the Openocd MCP Server, which means it retrieves data without modifying state.
Register the Openocd MCP server in PolicyLayer and add a rule for debug_status: 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.
debug_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the debug_status 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.
Set action: deny in the PolicyLayer policy for debug_status. 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.
debug_status 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.
Start from Openocd, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Openocd tools catalogued and risk-classified — across an index of 43,000+ MCP servers.