Get the current status of the mcp-debugger backend (state, PID, uptime, tool count, port).
AI agents call dev_server_status to retrieve information from Mcp Debugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic and status information about the debugger backend. It has no side effects, does not execute code, does not modify data, and does not delete anything. It is a pure information-gathering operation, classifying as Read. Severity is low because exposing debugger status information poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'dev_server_status' and description 'Get the current status' indicate a query operation that retrieves state information (state, PID, uptime, tool count, port) without modifying or executing anything.
Attacks that exploit this kind of access
Get the current status of the mcp-debugger backend (state, PID, uptime, tool count, port). It is categorised as a Read tool in the Mcp Debugger MCP Server, which means it retrieves data without modifying state.
Register the Mcp Debugger MCP server in PolicyLayer and add a rule for dev_server_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 Mcp Debugger. Nothing to install.
dev_server_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 dev_server_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 dev_server_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.
dev_server_status is provided by the Mcp Debugger MCP server (@debugmcp/mcp-debugger). 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 →