close_heapsnapshot
Closes a previously loaded memory heapsnapshot, freeing its memory.
This record as markdown: /tools/async23-chrome-devtools-mcp/close-heapsnapshot.md
What close_heapsnapshot does on Chrome Devtools
AI agents call close_heapsnapshot to permanently remove resources in Chrome Devtools, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why close_heapsnapshot is rated Critical
Closing and freeing a heap snapshot is an irreversible operation that discards the in-memory snapshot data. However, the blast radius is low because it only affects a diagnostic/analysis artifact (a memory snapshot), not production data or system state. Severity is low since at worst an analyst loses a snapshot they would need to retake.
From the tool's definition 'Closes a previously loaded memory heapsnapshot, freeing its memory' — the action is irreversible (the snapshot data is freed/discarded)
Attacks that exploit this kind of access
The rule that runs close_heapsnapshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For close_heapsnapshot, this is the rule to start with:
close_heapsnapshot is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every close_heapsnapshot call is checked against it from then on.
Questions about close_heapsnapshot
Closes a previously loaded memory heapsnapshot, freeing its memory. It is categorised as a Destructive tool in the Chrome Devtools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for close_heapsnapshot: 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 Chrome Devtools. Nothing to install.
close_heapsnapshot is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the close_heapsnapshot 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 close_heapsnapshot. 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.
close_heapsnapshot is provided by the Chrome Devtools MCP server (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome Devtools, and thousands of servers like it.
Across the catalogue