Get a backtrace.
AI agents call backtrace to retrieve information from WineDbg MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The backtrace tool retrieves debugging information (call stack) from a running process under winedbg. This is a read-only diagnostic operation with no side effects on the debugged application, its memory, or execution state. While debuggers can be powerful tools, this specific operation simply queries and returns information without executing code, modifying data, or triggering external actions.
From the tool's definition Tool name 'backtrace' and description 'Get a backtrace.' indicates a query operation that retrieves stack trace information from a debugger without modifying any state.
Attacks that exploit this kind of access
Get a backtrace. It is categorised as a Read tool in the WineDbg MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WineDbg MCP Server MCP server in PolicyLayer and add a rule for backtrace: 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 WineDbg MCP Server. Nothing to install.
backtrace 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 backtrace 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 backtrace. 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.
backtrace is provided by the WineDbg MCP Server MCP server (maci0/mcp-winedbg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
backtrace is one line of WineDbg MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →