Delete a Home Assistant automation
AI agents call delete_automation to permanently remove resources in Home Assistant MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of automations is an irreversible destructive action. Once deleted, the automation is removed and cannot be undone without manual recreation. While the blast radius is limited to a single smart home automation rule (not system-critical), the irreversible nature and potential to disable important home automation logic (e.g., security, climate control) justifies 'high' severity.
From the tool's definition Tool name 'delete_automation' and description 'Delete a Home Assistant automation' explicitly perform irreversible deletion of automation configurations.
Attacks that exploit this kind of access
Delete a Home Assistant automation. It is categorised as a Destructive tool in the Home Assistant MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Home Assistant MCP Server 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 Home Assistant MCP Server. 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 Home Assistant MCP Server MCP server (mjrestivo16/mcp-homeassistant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →