access_unlock_door
A execute tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/access-unlock-door.md
What access_unlock_door does on UniFi Access MCP
AI agents invoke access_unlock_door 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 access_unlock_door is rated High
Unlocking a door triggers a physical, real-world action (opening a door lock) that constitutes an external operation with immediate physical security implications. This fits Execute (triggering external operations). The blast radius is high because an AI agent misusing this tool could unlock doors without authorization, compromising physical security.
From the tool's definition Tool name 'access_unlock_door' on a server managing 'UniFi Access doors'. Description is empty.
Attacks that exploit this kind of access
The rule that runs access_unlock_door 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 access_unlock_door, this is the rule to start with:
access_unlock_door 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 access_unlock_door call is checked against it from then on.
Questions about access_unlock_door
access_unlock_door 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 access_unlock_door: 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.
access_unlock_door 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 access_unlock_door 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 access_unlock_door. 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.
access_unlock_door 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