Get exception summary for a dump_id (code, name, type, fault address).
AI agents call get_exception_info to retrieve information from DumpAnalysisMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns structured information (exception code, name, type, fault address) without modifying any data, executing code, or triggering side effects. It is a simple read operation that retrieves diagnostic metadata. The low severity reflects minimal blast radius—misuse would only expose debugging information already present in the dump.
From the tool's definition Tool name 'get_exception_info' and description 'Get exception summary for a dump_id (code, name, type, fault address)' indicate retrieval of static metadata about an exception from an already-registered crash dump.
Documented attack patterns abuse exactly the kind of access get_exception_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DumpAnalysisMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_exception_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_exception_info": {}
}
}get_exception_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get exception summary for a dump_id (code, name, type, fault address). It is categorised as a Read tool in the DumpAnalysisMCP MCP Server, which means it retrieves data without modifying state.
Register the DumpAnalysis MCP server in PolicyLayer and add a rule for get_exception_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 DumpAnalysisMCP. Nothing to install.
get_exception_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_exception_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_exception_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_exception_info is provided by the DumpAnalysis MCP server (kindtis/dumpanalysismcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DumpAnalysisMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 DumpAnalysisMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.