add_automation_rule
AI agents use add_automation_rule to create or update resources in AC Infinity MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AC Infinity MCP environment.
The tool creates new automation rules that control physical devices (fans, ports). While the empty description reduces confidence slightly, the naming pattern and sibling tools indicate this performs a data creation/modification action. It is reversible (rules can be deleted or modified later), so it is Write rather than Execute or Destructive.
From the tool's definition The tool name is 'add_automation_rule' with an empty description. Based on sibling tools like 'create_advance_automation', 'delete_advance_automation', 'delete_automation_rule', and 'enable_advance_automation', this tool creates or modifies automation rules…
Attacks that exploit this kind of access
add_automation_rule. It is categorised as a Write tool in the AC Infinity MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AC Infinity MCP server in PolicyLayer and add a rule for add_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.
add_automation_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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 →