List threads for dump_id with faulting metadata, top frame, and CPU user time.
AI agents call get_thread_list 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 retrieves and lists thread information from an already-loaded crash dump. It performs no mutations, executions, or destructive operations. The verb 'List' combined with the read-only nature of the operation (returning metadata about threads) clearly places it in the Read category. The severity is low because retrieving analysis data from a crash dump poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states 'List threads for dump_id with faulting metadata, top frame, and CPU user time' — a retrieval operation that queries existing dump data and returns structured metadata about threads without modifying anything.
Documented attack patterns abuse exactly the kind of access get_thread_list 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_thread_list:
{
"version": "1",
"default": "deny",
"tools": {
"get_thread_list": {}
}
}get_thread_list 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.
List threads for dump_id with faulting metadata, top frame, and CPU user time. 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_thread_list: 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_thread_list 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_thread_list 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_thread_list. 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_thread_list 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.