snapshot_rollback

Rollback a dataset to a snapshot (destructive — requires confirm)

SERVERTruenas SOURCEspranab/truenas-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/spranab-truenas-mcp/snapshot-rollback.md

WHAT IT DOES

What snapshot_rollback does on Truenas

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

RISK

Why snapshot_rollback is rated Critical

Rolling back a dataset to a snapshot permanently destroys all data written after that snapshot was taken. This is irreversible and affects potentially large storage volumes, making it critical severity. The description itself flags it as destructive.

From the tool's definition 'Rollback a dataset to a snapshot (destructive — requires confirm)' — explicitly labeled destructive; rolling back a dataset overwrites all current data irreversibly

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs snapshot_rollback 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_rollback, this is the rule to start with:

snapshot_rollback Hidden

snapshot_rollback is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "snapshot_rollback"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Truenas, apply this rule, and every snapshot_rollback call is checked against it from then on.

FAQ

Questions about snapshot_rollback

What does the snapshot_rollback tool do? +

Rollback a dataset to a 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.

How do I enforce a policy on snapshot_rollback? +

Register the Truenas MCP server in PolicyLayer and add a rule for snapshot_rollback: 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_rollback? +

snapshot_rollback 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_rollback? +

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

Set action: deny in the PolicyLayer policy for snapshot_rollback. 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_rollback? +

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

KEEP EXPLORING

More on Truenas, and thousands of servers like it.

This server

All 279 Truenas tools → Critical-risk tools on this server →

Across the catalogue

delete_snapshot on Why Did You Render → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →