delete_automation_rule
AI agents call delete_automation_rule to permanently remove resources in AC Infinity MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the description is empty, the tool name unambiguously performs a destructive operation (delete). In an AC Infinity controller system managing grow environments or HVAC, automation rules are critical infrastructure. Deletion is irreversible and would impact system functionality.
From the tool's definition Tool name 'delete_automation_rule' explicitly indicates irreversible deletion of an automation rule. The server context shows this MCP connects to AC Infinity environmental controllers that manage fan speeds and port states.
Attacks that exploit this kind of access
delete_automation_rule. It is categorised as a Destructive tool in the AC Infinity MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AC Infinity MCP server in PolicyLayer and add a rule for delete_automation_rule: 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 AC Infinity MCP. Nothing to install.
delete_automation_rule 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 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_rule. 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_rule is provided by the AC Infinity MCP server (ober37/ac-infinity-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 →