Get stack frames for a selected thread in dump_id (default: crashing thread; thread_id uses WinDbg index first, OS TID fallback).
AI agents call get_stack_trace to retrieve information from DumpAnalysisMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries structured data (stack frames for a thread) from a crash dump that has already been analyzed. It has no side effects, does not modify data, execute code, or delete anything. It is purely informational—typical of Read category tools like 'get', 'fetch', or 'list'.
From the tool's definition Tool name 'get_stack_trace' and description indicate retrieval of stack frame data from an already-loaded crash dump. Action is 'Get' with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access get_stack_trace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DumpAnalysisMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_stack_trace:
{
"version": "1",
"default": "deny",
"tools": {
"get_stack_trace": {}
}
}get_stack_trace is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get stack frames for a selected thread in dump_id (default: crashing thread; thread_id uses WinDbg index first, OS TID fallback). It is categorised as a Read tool in the DumpAnalysisMCP MCP Server, which means it retrieves data without modifying state.
Register the DumpAnalysis MCP server in PolicyLayer and add a rule for get_stack_trace: 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 DumpAnalysisMCP. Nothing to install.
get_stack_trace 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_stack_trace 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_stack_trace. 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_stack_trace is provided by the DumpAnalysis MCP server (kindtis/dumpanalysismcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DumpAnalysisMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 DumpAnalysisMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.