set_humidity_automation
AI agents use set_humidity_automation 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.
Based on the tool name and server context, this tool likely creates or modifies a humidity-based automation rule for AC Infinity controllers. This falls under Write as it sets/configures automation parameters. The severity is high because misconfigured humidity automation in a grow environment can cause significant plant damage or mold issues. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'set_humidity_automation' combined with server context of adjusting fan speeds, port states, and automation rules for environmental controllers.
Attacks that exploit this kind of access
set_humidity_automation. 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 set_humidity_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 AC Infinity MCP. Nothing to install.
set_humidity_automation 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 set_humidity_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 set_humidity_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.
set_humidity_automation 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 →