Retrieves the live debugging snapshot from a connected DAP session:
AI agents call inspect_runtime_state to retrieve information from Debugging MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves runtime state information for diagnostic purposes without executing code, modifying data, or causing side effects. Even though it accesses a live debugging session, the action is purely observational. The parent server explicitly prevents destructive operations, and this tool's read-only nature aligns with safe debugging introspection.
From the tool's definition Tool description states it 'Retrieves the live debugging snapshot from a connected DAP session' — a retrieval operation with no modification of state. The verb 'Retrieves' and the noun 'snapshot' indicate read-only access to debugger state.
Attacks that exploit this kind of access
Retrieves the live debugging snapshot from a connected DAP session:. It is categorised as a Read tool in the Debugging MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Debugging MCP Server MCP server in PolicyLayer and add a rule for inspect_runtime_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 Debugging MCP Server. Nothing to install.
inspect_runtime_state 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 inspect_runtime_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.
Set action: deny in the PolicyLayer policy for inspect_runtime_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.
inspect_runtime_state is provided by the Debugging MCP Server MCP server (luischang07/debugging-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 →