set_port_mode
AI agents invoke set_port_mode to trigger actions in AC Infinity MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name strongly suggests it changes the mode/state of a physical controller port (e.g., fan, outlet). This is an Execute-level action because it triggers an external physical operation on connected hardware. The description is empty, which lowers confidence, but sibling tools like 'break_out_of_automation' and 'apply_grow_stage_template' confirm this server controls physical devices.
From the tool's definition Tool name 'set_port_mode' on a server described as able to 'adjust fan speeds or port states using natural language' — the name implies changing the operational mode of a physical device port.
Attacks that exploit this kind of access
set_port_mode. It is categorised as a Execute tool in the AC Infinity MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AC Infinity MCP server in PolicyLayer and add a rule for set_port_mode: 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_port_mode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the set_port_mode 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_port_mode. 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_port_mode 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 →