New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

sandbox_delete_template_snapshot

Delete a derived template by derivedId. Fails with 409 DerivedTemplateInUse while children created from it are alive (starting/running/suspended) — destroy them first. Does not affect the source box.

SERVEREasyBits SOURCE@easybits.cloud/mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/sandbox-delete-template-snapshot.md

What sandbox_delete_template_snapshot does on EasyBits

AI agents call sandbox_delete_template_snapshot to permanently remove resources in EasyBits, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why sandbox_delete_template_snapshot is rated Critical

Irreversibly deletes template snapshots; cannot be undone once children are cleaned up.

From the tool's definition Delete a derived template by derivedId. Fails with 409 DerivedTemplateInUse while children created from it are alive

Questions about sandbox_delete_template_snapshot

What does the sandbox_delete_template_snapshot tool do? +

Delete a derived template by derivedId. Fails with 409 DerivedTemplateInUse while children created from it are alive (starting/running/suspended) — destroy them first. Does not affect the source box. It is categorised as a Destructive tool in the EasyBits 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 sandbox_delete_template_snapshot? +

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

What risk level is sandbox_delete_template_snapshot? +

sandbox_delete_template_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 sandbox_delete_template_snapshot? +

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

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

sandbox_delete_template_snapshot is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on EasyBits, 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 EasyBits'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.