get_async_windbg_command_status

Get the current status of an asynchronously running CDB command.

Server Dump Analyzer zuohuiyang/dump-analyzer-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_async_windbg_command_status does on Dump Analyzer

AI agents call get_async_windbg_command_status to retrieve information from Dump Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_async_windbg_command_status needs a policy

This tool retrieves status information about an existing async operation—a pure query with no side effects. The verb 'Get' and the focus on retrieving 'status' (not executing, modifying, or deleting) clearly place it in the Read category. Even though the broader server enables crash dump analysis via debugger commands, this specific tool is limited to status polling, which carries minimal risk if misused by an agent.

From the tool's definition Tool name 'get_async_windbg_command_status' and description 'Get the current status of an asynchronously running CDB command' indicate a read-only operation that queries status without modifying or executing commands.

Questions about get_async_windbg_command_status

What does the get_async_windbg_command_status tool do? +

Get the current status of an asynchronously running CDB command. It is categorised as a Read tool in the Dump Analyzer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_async_windbg_command_status? +

Register the Dump Analyzer MCP server in PolicyLayer and add a rule for get_async_windbg_command_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 Dump Analyzer. Nothing to install.

What risk level is get_async_windbg_command_status? +

get_async_windbg_command_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_async_windbg_command_status? +

Yes. Add a rate_limit block to the get_async_windbg_command_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.

How do I block get_async_windbg_command_status completely? +

Set action: deny in the PolicyLayer policy for get_async_windbg_command_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.

What MCP server provides get_async_windbg_command_status? +

get_async_windbg_command_status is provided by the Dump Analyzer MCP server (zuohuiyang/dump-analyzer-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.