Get loaded modules and overall symbol quality for a dump_id.
AI agents call get_module_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 structured diagnostic information (loaded modules and symbol quality metadata) from an already-captured crash dump. It has no side effects, does not execute code, modify data, or trigger external operations. It is a pure read operation fitting the 'Read' category. Low severity because the information returned is diagnostic metadata with limited blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_module_list' with description 'Get loaded modules and overall symbol quality for a dump_id' — this is a retrieval operation that queries and returns data about modules without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_module_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_module_list:
{
"version": "1",
"default": "deny",
"tools": {
"get_module_list": {}
}
}get_module_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.
Get loaded modules and overall symbol quality for a dump_id. 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_module_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_module_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_module_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_module_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_module_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.