take-heap-snapshot · Debugger MCP Server MCP: Risk & Policy

WHAT IT DOES

What take-heap-snapshot does on Debugger MCP Server

AI agents invoke take-heap-snapshot to trigger actions in Debugger 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 IT NEEDS A POLICY

Why take-heap-snapshot needs a policy

Taking a heap snapshot invokes an active Chrome DevTools operation against a running browser/application process. It is not a passive read; it triggers an instrumentation action with side effects (CPU/memory overhead, potential pause of execution). It does not delete data or move money, making Execute the most appropriate category.

From the tool's definition 'Take a detailed heap snapshot using Chrome DevTools' — triggers an external browser operation via Chrome DevTools Protocol to capture heap state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

take-heap-snapshot Rate-limited

take-heap-snapshot 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": {
    "take-heap-snapshot": {
      "limits": [
        {
          "counter": "take-heap-snapshot_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 Debugger MCP Server, so you can run agents against it safely.

FAQ

Questions about take-heap-snapshot

What does the take-heap-snapshot tool do? +

Take a detailed heap snapshot using Chrome DevTools for memory analysis. It is categorised as a Execute tool in the Debugger MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on take-heap-snapshot? +

Register the Debugger MCP Server MCP server in PolicyLayer and add a rule for take-heap-snapshot: 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 Debugger MCP Server. Nothing to install.

What risk level is take-heap-snapshot? +

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

Can I rate-limit take-heap-snapshot? +

Yes. Add a rate_limit block to the take-heap-snapshot 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 take-heap-snapshot completely? +

Set action: deny in the PolicyLayer policy for take-heap-snapshot. 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 take-heap-snapshot? +

take-heap-snapshot is provided by the Debugger MCP Server MCP server (phoenixrr2113/debugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.