检查 WinDbg 插件是否正在运行
AI agents call check_connection 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 performs a diagnostic read operation to verify plugin connectivity. It has no side effects, does not execute code, and does not modify system state. It is analogous to a ping or status query, making it a Read category tool with low severity due to minimal blast radius from misuse.
From the tool's definition Tool name 'check_connection' and description '检查 WinDbg 插件是否正在运行' (Check if WinDbg plugin is running) indicate a status/health check operation that queries the connection state without modifying any data or executing commands.
Attacks that exploit this kind of access
检查 WinDbg 插件是否正在运行. 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 check_connection: 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.
check_connection 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 check_connection 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 check_connection. 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.
check_connection 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 →