snapshot_delete
Delete a ZFS snapshot (destructive — requires confirm)
This record as markdown: /tools/spranab-truenas-mcp/snapshot-delete.md
What snapshot_delete does on Truenas
AI agents call snapshot_delete to permanently remove resources in Truenas, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why snapshot_delete is rated Critical
The tool explicitly deletes a ZFS snapshot and is labeled as destructive. ZFS snapshots are point-in-time backups; deleting them is irreversible and can result in permanent loss of recovery points, making this a high-severity destructive action.
From the tool's definition Delete a ZFS snapshot (destructive — requires confirm)
Attacks that exploit this kind of access
The rule that runs snapshot_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snapshot_delete, this is the rule to start with:
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 Truenas, apply this rule, and every snapshot_delete call is checked against it from then on.
Questions about snapshot_delete
Delete a ZFS snapshot (destructive — requires confirm). It is categorised as a Destructive tool in the Truenas MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Truenas 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 Truenas. 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 Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Truenas, and thousands of servers like it.
Across the catalogue