v8_heap_snapshot_delete
Delete persisted V8 heap snapshot artifact files (.heapsnapshot data + .meta.json sidecar) and drop the matching in-memory cache entry. Use deleteAll=true to remove every persisted snapshot. Does not affect the live V8 heap.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/v8-heap-snapshot-delete.md
What v8_heap_snapshot_delete does on Jshookmcp
AI agents call v8_heap_snapshot_delete to permanently remove resources in Jshookmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why v8_heap_snapshot_delete is rated Critical
Irreversibly deletes snapshot files and cache entries; supports bulk deletion via deleteAll=true.
From the tool's definition Delete persisted V8 heap snapshot artifact files… drop the matching in-memory cache
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs v8_heap_snapshot_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For v8_heap_snapshot_delete, this is the rule to start with:
v8_heap_snapshot_delete 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 Jshookmcp, apply this rule, and every v8_heap_snapshot_delete call is checked against it from then on.
Questions about v8_heap_snapshot_delete
Delete persisted V8 heap snapshot artifact files (.heapsnapshot data + .meta.json sidecar) and drop the matching in-memory cache entry. Use deleteAll=true to remove every persisted snapshot. Does not affect the live V8 heap. It is categorised as a Destructive tool in the Jshookmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jshook MCP server in PolicyLayer and add a rule for v8_heap_snapshot_delete: 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 Jshookmcp. Nothing to install.
v8_heap_snapshot_delete 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 v8_heap_snapshot_delete 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 v8_heap_snapshot_delete. 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.
v8_heap_snapshot_delete is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
Across the catalogue