unifi_set_outlet_state
A execute tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-set-outlet-state.md
What unifi_set_outlet_state does on UniFi Access MCP
AI agents invoke unifi_set_outlet_state to trigger actions in UniFi Access 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.
Why unifi_set_outlet_state is rated High
The tool name suggests it controls the power state of an outlet (on/off), which is an external physical operation. This falls under Execute as it triggers external hardware operations. However, the description is empty, lowering confidence. The context of a UniFi Access MCP server (managing doors, credentials, access control) makes this tool somewhat out of place, but outlet control is a known UniFi feature.
From the tool's definition Tool name 'unifi_set_outlet_state' implies setting/changing the state of an electrical outlet; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs unifi_set_outlet_state safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UniFi Access MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unifi_set_outlet_state, this is the rule to start with:
unifi_set_outlet_state stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UniFi Access MCP, apply this rule, and every unifi_set_outlet_state call is checked against it from then on.
Questions about unifi_set_outlet_state
unifi_set_outlet_state is a execute tool on the UniFi Access MCP server. It is categorised as a Execute tool in the UniFi Access MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the UniFi Access MCP server in PolicyLayer and add a rule for unifi_set_outlet_state: 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 UniFi Access MCP. Nothing to install.
unifi_set_outlet_state 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 unifi_set_outlet_state 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 unifi_set_outlet_state. 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.
unifi_set_outlet_state is provided by the UniFi Access MCP server (pypi:unifi-protect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UniFi Access, and thousands of servers like it.
Across the catalogue