delete_automation
Delete an automation by id. Auto-reloads automations afterwards.
This record as markdown: /tools/fistacho-ha-nexus-agent/delete-automation.md
What delete_automation does on Ha Nexus Agent
AI agents call delete_automation 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_automation is rated Critical
Automations are persistent configurations that users intentionally set up to automate home behavior (lights, doors, sensors, etc.). Deleting an automation cannot be undone via the tool itself and would require manual reconfiguration. An AI agent calling this without explicit user intent could cause loss of important home automation logic (security automations, scheduling, etc.).
From the tool's definition 'Delete an automation by id' — removes an automation configuration irreversibly. The description confirms deletion without undo mechanism ('Auto-reloads automations afterwards' indicates the change is finalized).
Attacks that exploit this kind of access
The rule that runs delete_automation 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_automation, this is the rule to start with:
delete_automation 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_automation call is checked against it from then on.
Questions about delete_automation
Delete an automation by id. Auto-reloads automations afterwards. 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_automation: 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_automation 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_automation 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_automation. 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_automation 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