New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cloud_backup_delete

Delete a cloud backup task (destructive — requires confirm)

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-delete.md

What cloud_backup_delete does on Truenas

AI agents call cloud_backup_delete 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 cloud_backup_delete is rated Critical

This tool permanently removes a cloud backup task, which is an irreversible operation. Although confirmation is required, deletion of backup configurations could result in loss of recovery capabilities. This is categorized as Destructive rather than Write because it cannot be undone without external intervention (e.g., restore from logs).

From the tool's definition Tool name is 'cloud_backup_delete' and description explicitly states 'Delete a cloud backup task (destructive — requires confirm)'. The word 'destructive' in the description and the delete action confirm irreversible removal of data.

Questions about cloud_backup_delete

What does the cloud_backup_delete tool do? +

Delete a cloud backup task (destructive — requires confirm). 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_delete? +

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

cloud_backup_delete 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_delete? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Truenas's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.