Get the stack backtrace (standard GDB backtrace).
AI agents call gdb_get_backtrace to retrieve information from Gdb Multiarch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Stack backtrace retrieval is a read-only debugging operation that queries the current execution state without side effects. However, severity is elevated to medium because: (1) the tool operates within a debugger context with full process access; (2) backtrace information can leak sensitive details about process layout, function names, and memory addresses; (3) in a Switch emulation/debugging context, this could…
From the tool's definition Tool name 'gdb_get_backtrace' and description 'Get the stack backtrace (standard GDB backtrace)' indicates retrieval of debugging information without modification. The action is purely informational—reading the call stack.
Attacks that exploit this kind of access
Get the stack backtrace (standard GDB backtrace). It is categorised as a Read tool in the Gdb Multiarch MCP Server, which means it retrieves data without modifying state.
Register the Gdb Multiarch MCP server in PolicyLayer and add a rule for gdb_get_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 Gdb Multiarch. Nothing to install.
gdb_get_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 gdb_get_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 gdb_get_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.
gdb_get_backtrace is provided by the Gdb Multiarch MCP server (sbergeron42/gdb-multiarch-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 →