AI agents call debugpy_status to retrieve information from Debugpy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates a status/query operation with no obvious write, execute, or destructive capability. However, confidence is moderate due to the missing description, and severity is medium rather than low because debugpy attachment grants process-level access—even read operations on debugging state could expose sensitive runtime information, environment variables, or source code context from running processes.
From the tool's definition Tool name 'debugpy_status' with empty description suggests a status query operation. In the context of a debugpy MCP server that attaches to Python processes, a status tool would retrieve debugging session state, breakpoint information, or process state…
Attacks that exploit this kind of access
debugpy_status. It is categorised as a Read tool in the Debugpy MCP Server, which means it retrieves data without modifying state.
Register the Debugpy MCP server in PolicyLayer and add a rule for debugpy_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 Debugpy. Nothing to install.
debugpy_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 debugpy_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 debugpy_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.
debugpy_status is provided by the Debugpy MCP server (will-garrett/debugpy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →