This record as markdown: /tools/fistacho-ha-nexus-agent/delete-backup.md
What delete_backup does on Ha Nexus Agent
AI agents call delete_backup to permanently remove resources in Ha Nexus Agent, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_backup is rated Critical
This tool permanently removes backup files, which cannot be undone. Backups are critical for disaster recovery in smart home systems. Unintended deletion could result in loss of configuration, automation rules, and system state that cannot be restored. This is irreversible data loss, placing it in the Destructive category with high severity.
From the tool's definition Tool name 'delete_backup' explicitly performs deletion. Description states 'Delete a backup by slug' — a direct destructive operation that irreversibly removes backup data.
Attacks that exploit this kind of access
The rule that runs delete_backup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ha Nexus Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_backup, this is the rule to start with:
delete_backup is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ha Nexus Agent, apply this rule, and every delete_backup call is checked against it from then on.
Questions about delete_backup
Delete a backup by slug. It is categorised as a Destructive tool in the Ha Nexus Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for delete_backup: 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 Ha Nexus Agent. Nothing to install.
delete_backup is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_backup 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 delete_backup. 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.
delete_backup is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ha Nexus Agent, and thousands of servers like it.
Across the catalogue