Delete a saved snapshot by label. This frees disk space and means the next vm_create with this label will start fresh.
AI agents call snapshot_delete to permanently remove resources in Taw Computer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool irreversibly deletes a saved snapshot, freeing disk space and permanently removing the saved state. This is an unrecoverable action — once deleted, the snapshot cannot be restored. High severity because it could wipe environment state an agent or user depends on.
From the tool's definition Delete a saved snapshot by label...the next vm_create with this label will start fresh
Documented attack patterns abuse exactly the kind of access snapshot_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Taw Computer, and nothing reaches the server without passing your rules. This is the rule we recommend for snapshot_delete:
{
"version": "1",
"default": "deny",
"hide": [
"snapshot_delete"
]
} snapshot_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a saved snapshot by label. This frees disk space and means the next vm_create with this label will start fresh. It is categorised as a Destructive tool in the Taw Computer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Taw Computer MCP server in PolicyLayer and add a rule for 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 Taw Computer. Nothing to install.
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 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 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.
snapshot_delete is provided by the Taw Computer MCP server (tawgroup/taw-computer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Taw Computer, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 Taw Computer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.