list_crash_dumps
List all available crash dumps
This record as markdown: /tools/42research-dynamic-mcp/list-crash-dumps.md
What list_crash_dumps does on Dynamic MCP Server
AI agents call list_crash_dumps to retrieve information from Dynamic MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_crash_dumps is rated Low
This tool performs a query/enumeration operation returning crash dump metadata. It has no side effects, does not execute code or commands, does not modify data, and does not delete or move resources. The blast radius of misuse is minimal—an agent could discover crash dumps but cannot directly harm systems through this tool alone. Classified as Read with low severity.
From the tool's definition Tool name 'list_crash_dumps' combined with description 'List all available crash dumps' indicates a read-only operation that retrieves and enumerates data without modification or execution of code.
Attacks that exploit this kind of access
The rule that runs list_crash_dumps safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dynamic MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_crash_dumps, this is the rule to start with:
list_crash_dumps is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dynamic MCP Server, apply this rule, and every list_crash_dumps call is checked against it from then on.
Questions about list_crash_dumps
List all available crash dumps. It is categorised as a Read tool in the Dynamic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dynamic MCP Server MCP server in PolicyLayer and add a rule for list_crash_dumps: 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 Dynamic MCP Server. Nothing to install.
list_crash_dumps 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 list_crash_dumps 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 list_crash_dumps. 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.
list_crash_dumps is provided by the Dynamic MCP Server MCP server (42research/dynamic_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dynamic MCP Server, and thousands of servers like it.
This server
Across the catalogue