Remove an automation by ID
AI agents call delete_automation to permanently remove resources in ClawDaemon MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes automation rules that orchestrate background operations. Unlike reversible Write operations, deletion cannot be undone. The blast radius is significant because removing automations could stop critical scheduled tasks, webhooks, or message routing indefinitely until manually reconfigured.
From the tool's definition Tool name is 'delete_automation' with description 'Remove an automation by ID'. The word 'Remove' indicates irreversible deletion of automation configurations that persist across sessions and control scheduled jobs, webhooks, and messaging across 23+…
Attacks that exploit this kind of access
Remove an automation by ID. It is categorised as a Destructive tool in the ClawDaemon MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ClawDaemon 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 ClawDaemon MCP. 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 ClawDaemon MCP server (mordiaky/clawdaemon-mcp). 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 →