Get current debugging session information
AI agents call get-debug-session to retrieve information from Debugger MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves debugging session metadata and state information. It performs no writes, deletions, code execution, or side effects—it simply queries and returns current debugging context. This is a standard read operation with minimal security risk, suitable for monitoring and inspection purposes.
From the tool's definition Tool name 'get-debug-session' and description 'Get current debugging session information' indicate retrieval of existing session state without modification. The verb 'Get' and lack of any modification language confirm this is a read operation.
Attacks that exploit this kind of access
Get current debugging session information. It is categorised as a Read tool in the Debugger MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Debugger MCP Server MCP server in PolicyLayer and add a rule for get-debug-session: 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 Debugger MCP Server. Nothing to install.
get-debug-session 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 get-debug-session 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 get-debug-session. 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.
get-debug-session is provided by the Debugger MCP Server MCP server (phoenixrr2113/debugger-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 →