Critical Risk →

app_rollback

Rollback an app to a previous version. This is a DESTRUCTIVE operation. The

How to control app_rollback ↓

What app_rollback does on Truenas

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

Critical Risk

Why app_rollback needs a policy

The description explicitly labels this a DESTRUCTIVE operation. Rolling back an application to a previous version overwrites the current state irreversibly (the current version/state is lost), making it a destructive action with high blast radius as it can break running services.

From the tool's definition Rollback an app to a previous version. This is a DESTRUCTIVE operation.

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

How to control app_rollback

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 app_rollback:

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

app_rollback 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 app_rollback

What does the app_rollback tool do? +

Rollback an app to a previous version. This is a DESTRUCTIVE operation. The. 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 app_rollback? +

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

app_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 app_rollback? +

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

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

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

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.