Get stack trace from a coredump using GDB
AI agents call get_stacktrace to retrieve information from systemd-coredump MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads and analyzes diagnostic data (stack trace) from core dump files. While core dumps may contain sensitive information (memory contents, credentials, source code details), the action itself is read-only with no side effects on the system or data. Severity is medium rather than low because core dumps can expose sensitive information, but the tool performs only information retrieval.
From the tool's definition Tool description states 'Get stack trace from a coredump using GDB' — this retrieves debugging information from an existing core dump without modifying or executing code.
Attacks that exploit this kind of access
Get stack trace from a coredump using GDB. It is categorised as a Read tool in the systemd-coredump MCP Server MCP Server, which means it retrieves data without modifying state.
Register the systemd-coredump MCP Server MCP server in PolicyLayer and add a rule for get_stacktrace: 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 systemd-coredump MCP Server. Nothing to install.
get_stacktrace 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_stacktrace 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_stacktrace. 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_stacktrace is provided by the systemd-coredump MCP Server MCP server (signal-slot/mcp-systemd-coredump). 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 →