start_crash_session
Start a new crash session with a specific dump
This record as markdown: /tools/42research-dynamic-mcp/start-crash-session.md
What start_crash_session does on Dynamic MCP Server
AI agents invoke start_crash_session to trigger actions in Dynamic MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why start_crash_session is rated High
This tool triggers execution of an external debugging utility (crash) whose effects depend on the dump argument and subsequent commands. While not immediately destructive, it enables Execute-category operations (kernel inspection, bpftrace script execution) with potentially wide blast radius if an agent launches sessions on unvetted dumps or combines them with destructive kernel modifications.
From the tool's definition The tool 'start_crash_session' initiates a crash analysis session interfacing with the real crash utility for kernel debugging. Sibling tools like 'crash_command' and 'execute_bpftrace_script' confirm this server executes arbitrary debugging operations.
Attacks that exploit this kind of access
The rule that runs start_crash_session 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 start_crash_session, this is the rule to start with:
start_crash_session stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 start_crash_session call is checked against it from then on.
Questions about start_crash_session
Start a new crash session with a specific dump. It is categorised as a Execute tool in the Dynamic MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Dynamic MCP Server MCP server in PolicyLayer and add a rule for start_crash_session: 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.
start_crash_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_crash_session 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 start_crash_session. 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.
start_crash_session 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.
Across the catalogue