start_analysis_session · Dump Analyzer MCP: Risk & Policy

WHAT IT DOES

What start_analysis_session does on Dump Analyzer

AI agents invoke start_analysis_session to trigger actions in Dump Analyzer. 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 IT NEEDS A POLICY

Why start_analysis_session needs a policy

Loading and analyzing crash dumps via CDB commands constitutes executing external operations whose effects depend on arguments (which dump file, what symbols). While read-only in isolation, crash dump analysis is an Execute action because it invokes the Windows debugger infrastructure to perform dynamic analysis operations.

From the tool's definition Tool starts a crash dump analysis session by loading dump files and symbols through WinDbg/CDB commands. The server description explicitly states it 'Enables AI agents to analyze crash dumps via CDB commands', which are executable debugger operations that can…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_analysis_session Rate-limited

start_analysis_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_analysis_session": {
      "limits": [
        {
          "counter": "start_analysis_session_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dump Analyzer, so you can run agents against it safely.

FAQ

Questions about start_analysis_session

What does the start_analysis_session tool do? +

Start a crash dump analysis session and load the dump file and symbols. It is categorised as a Execute tool in the Dump Analyzer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_analysis_session? +

Register the Dump Analyzer MCP server in PolicyLayer and add a rule for start_analysis_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 Dump Analyzer. Nothing to install.

What risk level is start_analysis_session? +

start_analysis_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_analysis_session? +

Yes. Add a rate_limit block to the start_analysis_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.

How do I block start_analysis_session completely? +

Set action: deny in the PolicyLayer policy for start_analysis_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.

What MCP server provides start_analysis_session? +

start_analysis_session is provided by the Dump Analyzer MCP server (zuohuiyang/dump-analyzer-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.