delete_snapshot

Deletes a saved render snapshot by name.

SERVERWhy Did You Render SOURCE0x1f320/why-did-you-render-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0x1f320-why-did-you-render-mcp/delete-snapshot.md

What delete_snapshot does on Why Did You Render

AI agents call delete_snapshot to permanently remove resources in Why Did You Render, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_snapshot is rated Critical

The tool removes stored snapshots without possibility of recovery. While snapshots are development artifacts rather than production data, deletion is permanent and cannot be undone. This makes it Destructive rather than Write. An AI agent could misuse this by deleting all snapshots, losing performance history and diagnostic data needed for debugging.

From the tool's definition Tool name 'delete_snapshot' combined with description 'Deletes a saved render snapshot by name' explicitly performs irreversible deletion of data.

Questions about delete_snapshot

What does the delete_snapshot tool do? +

Deletes a saved render snapshot by name. It is categorised as a Destructive tool in the Why Did You Render MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_snapshot? +

Register the Why Did You Render MCP server in PolicyLayer and add a rule for delete_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 Why Did You Render. Nothing to install.

What risk level is delete_snapshot? +

delete_snapshot is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_snapshot? +

Yes. Add a rate_limit block to the delete_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 delete_snapshot completely? +

Set action: deny in the PolicyLayer policy for delete_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 delete_snapshot? +

delete_snapshot is provided by the Why Did You Render MCP server (0x1f320/why-did-you-render-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Why Did You Render, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Why Did You Render's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.