Get detailed information about a specific coredump
AI agents call get_coredump_info 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.
Core dumps contain sensitive information including memory contents, process state, and potentially credentials or encryption keys. While this is a Read operation (no side effects), the severity is high because coredump data can expose significant security and privacy-sensitive information. An AI agent with unrestricted access could extract sensitive data from system memory snapshots.
From the tool's definition Tool name is 'get_coredump_info' and description states 'Get detailed information about a specific coredump'. The verb 'Get' and the read-only action of retrieving coredump details indicate no data modification or execution.
Attacks that exploit this kind of access
Get detailed information about a specific coredump. 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_coredump_info: 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_coredump_info 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_coredump_info 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_coredump_info. 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_coredump_info 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 →