获取当前调试器会话的信息
AI agents call get_debugger_info to retrieve information from WinDbg GUI 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 debugger session metadata (likely process info, target state, session parameters). It is a passive read operation with no side effects, modification of state, or execution of code. Even in a debugger context, gathering information about the current session poses minimal risk—it cannot crash, alter, or execute anything.
From the tool's definition Tool name 'get_debugger_info' and description indicating it retrieves information about the current debugger session. The action is purely informational—reading/inspecting debugger state without modification or execution.
Attacks that exploit this kind of access
获取当前调试器会话的信息. It is categorised as a Read tool in the WinDbg GUI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WinDbg GUI MCP Server MCP server in PolicyLayer and add a rule for get_debugger_info: 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 WinDbg GUI MCP Server. Nothing to install.
get_debugger_info 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_debugger_info 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_debugger_info. 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_debugger_info is provided by the WinDbg GUI MCP Server MCP server (jianqiaojia/windbg-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 →