diagnose_crash

Inspect a coredump (coredumpctl info): signal, exe, stacktrace head.

Server Sysprobe raindancer118/sysprobe-mcp
Category Read
Risk class Low
Parameters 00 required

What diagnose_crash does on Sysprobe

AI agents call diagnose_crash to retrieve information from Sysprobe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why diagnose_crash needs a policy

This tool reads diagnostic information from existing coredumps for analysis purposes. It queries system state (coredump data) without side effects, modification, deletion, or code execution. The description explicitly indicates it inspects and retrieves information only.

From the tool's definition Tool performs 'coredumpctl info' inspection which retrieves and displays coredump metadata (signal, exe, stacktrace) without modifying or executing anything. No mutating action flags mentioned in description.

Questions about diagnose_crash

What does the diagnose_crash tool do? +

Inspect a coredump (coredumpctl info): signal, exe, stacktrace head. It is categorised as a Read tool in the Sysprobe MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on diagnose_crash? +

Register the Sysprobe MCP server in PolicyLayer and add a rule for diagnose_crash: 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 Sysprobe. Nothing to install.

What risk level is diagnose_crash? +

diagnose_crash is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit diagnose_crash? +

Yes. Add a rate_limit block to the diagnose_crash 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.

How do I block diagnose_crash completely? +

Set action: deny in the PolicyLayer policy for diagnose_crash. 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.

What MCP server provides diagnose_crash? +

diagnose_crash is provided by the Sysprobe MCP server (raindancer118/sysprobe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.