cloud_backup_update

THE RISK

Medium Risk

Why cloud_backup_update needs a policy

This tool creates or modifies data reversibly by updating backup task configuration. While it has side effects (changing backup behavior), it is not destructive (data/configs can be reverted) and does not execute arbitrary code or move money. The 'high' severity reflects that misconfiguring cloud backups could compromise data protection strategy, affecting backup integrity and disaster recovery capabilities.

From the tool's definition Tool name is 'cloud_backup_update' and description states 'Update an existing cloud backup task' — this modifies configuration of a backup task reversibly without deleting it.

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

POLICY

How to control cloud_backup_update

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cloud_backup_update": {
      "limits": [
        {
          "counter": "cloud_backup_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

cloud_backup_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Truenas — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Truenas tools

Destructive acme_dns_authenticator_delete Delete an ACME DNS authenticator by its ID. Destructive alertservice_delete Delete an alert notification service by its ID. Use alertservice_list to find the ID. Destructive api_key_delete Delete an API key by its numeric ID. Use api_key_list to find the ID. This immediately rev Destructive app_delete Delete/uninstall an app. This is a DESTRUCTIVE operation. The Destructive bootenv_delete Delete a boot environment. This is a DESTRUCTIVE operation — the Destructive certificate_delete Delete a certificate by its ID. This is a DESTRUCTIVE operation — the Destructive cloud_backup_delete Delete a cloud backup task (destructive — requires confirm) Destructive cloudsync_credentials_delete Delete a cloud sync credential

All 279 Truenas tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cloud_backup_update

What does the cloud_backup_update tool do? +

Update an existing cloud backup task. It is categorised as a Write tool in the Truenas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cloud_backup_update? +

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

cloud_backup_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cloud_backup_update? +

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

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

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

CHECK YOUR STACK →