Run a cloud backup task now
AI agents invoke cloud_backup_run to trigger actions in Truenas. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool executes a backup operation, which is a real-time action that initiates data transfer and processing on external systems. While not destructive in the sense of deletion, it is an Execute action because it triggers an irreversible operational sequence. Severity is high because a malicious agent could exhaust cloud storage, incur unexpected costs, or disrupt backup schedules.
From the tool's definition Tool name and description indicate 'Run a cloud backup task now' — this triggers an external operation (cloud backup execution) whose effects depend on system state and backup configuration.
Documented attack patterns abuse exactly the kind of access cloud_backup_run gives an agent:
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_run:
{
"version": "1",
"default": "deny",
"tools": {
"cloud_backup_run": {
"limits": [
{
"counter": "cloud_backup_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}cloud_backup_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run a cloud backup task now. It is categorised as a Execute tool in the Truenas MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Truenas MCP server in PolicyLayer and add a rule for cloud_backup_run: 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.
cloud_backup_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cloud_backup_run 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 cloud_backup_run. 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.
cloud_backup_run 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.
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.