Critical Risk →

cloud_backup_abort

Abort a running cloud backup task

How to control cloud_backup_abort ↓

What cloud_backup_abort does on Truenas

AI agents call cloud_backup_abort 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 cloud_backup_abort needs a policy

Aborting a running backup task is an irreversible action — the in-progress backup operation is terminated and cannot be resumed from where it left off. This could result in incomplete or corrupted backup data, potentially leaving the system without a valid recent backup. The effect cannot be undone, placing it in the Destructive category.

From the tool's definition Abort a running cloud backup task

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

How to control cloud_backup_abort

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

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

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

What does the cloud_backup_abort tool do? +

Abort a running cloud backup 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 cloud_backup_abort? +

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

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

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

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

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