cloud_backup_abort

Abort a running cloud backup task

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/cloud-backup-abort.md

WHAT IT DOES

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.

RISK

Why cloud_backup_abort is rated Critical

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

cloud_backup_abort Hidden

cloud_backup_abort 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": [
    "cloud_backup_abort"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

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.

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

create_full_backup on Android Forensics ADB MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →