Critical Risk →

snapshot_task_delete

Delete a periodic snapshot task

How to control snapshot_task_delete ↓

What snapshot_task_delete does on Truenas

AI agents call snapshot_task_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.

Critical Risk

Why snapshot_task_delete needs a policy

Deleting a periodic snapshot task is irreversible. It not only removes the task configuration but also stops future automated snapshots from being created, which could lead to data loss if the snapshots were serving as the sole backup mechanism. This is a destructive action with high blast radius in a storage management context.

From the tool's definition 'Delete a periodic snapshot task' — permanently removes a scheduled snapshot task

Documented attack patterns abuse exactly the kind of access snapshot_task_delete gives an agent:

How to control snapshot_task_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and Truenas, and nothing reaches the server without passing your rules. This is the rule we recommend for snapshot_task_delete:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "snapshot_task_delete"
  ]
}

snapshot_task_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Truenas — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about snapshot_task_delete

What does the snapshot_task_delete tool do? +

Delete a periodic snapshot task. 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.

How do I enforce a policy on snapshot_task_delete? +

Register the Truenas MCP server in PolicyLayer and add a rule for snapshot_task_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.

What risk level is snapshot_task_delete? +

snapshot_task_delete 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 snapshot_task_delete? +

Yes. Add a rate_limit block to the snapshot_task_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.

How do I block snapshot_task_delete completely? +

Set action: deny in the PolicyLayer policy for snapshot_task_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.

What MCP server provides snapshot_task_delete? +

snapshot_task_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.

Enforce policy on every Truenas tool call.

Start from Truenas, 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.

279 Truenas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.