app_rollback
Rollback an app to a previous version. This is a DESTRUCTIVE operation. The
This record as markdown: /tools/spranab-truenas-mcp/app-rollback.md
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.
Why app_rollback is rated Critical
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.
Attacks that exploit this kind of access
The rule that runs app_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 app_rollback, this is the rule to start with:
app_rollback 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 app_rollback call is checked against it from then on.
Questions about app_rollback
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.
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.
app_rollback 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 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.
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.
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.
More on Truenas, and thousands of servers like it.
Across the catalogue