AI agents call debugger_status to retrieve information from GDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves status information about debuggers. It has no side effects, cannot execute code, modify data, or delete resources. The read-only nature and informational purpose place it firmly in the Read category with low severity, as an attacker cannot cause harm through status queries alone.
From the tool's definition Tool name 'debugger_status' and description 'Get status of available debuggers' indicates a query operation that retrieves state information without modification or execution.
Documented attack patterns abuse exactly the kind of access debugger_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for debugger_status:
{
"version": "1",
"default": "deny",
"tools": {
"debugger_status": {}
}
}debugger_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 status of available debuggers. It is categorised as a Read tool in the GDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GDB MCP Server MCP server in PolicyLayer and add a rule for debugger_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 GDB MCP Server. Nothing to install.
debugger_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 debugger_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 debugger_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.
debugger_status is provided by the GDB MCP Server MCP server (smadi0x86/mdb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 GDB MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 GDB MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.