access_get_door_status
Get current door lock/position status.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/access-get-door-status.md
What access_get_door_status does on UniFi Access MCP
AI agents call access_get_door_status to retrieve information from UniFi Access MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why access_get_door_status is rated Low
This tool performs a read-only operation—retrieving the current state of a door's lock and position. It has no side effects, does not execute commands, modify data, or trigger physical actions. The verb 'get' and lack of any mutation language confirm it is a safe information retrieval operation. Even in a security context, status queries pose minimal risk as they only expose current state information.
From the tool's definition Tool name 'access_get_door_status' and description 'Get current door lock/position status' indicate a query operation that retrieves real-time status information without modification.
Attacks that exploit this kind of access
The rule that runs access_get_door_status 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_get_door_status, this is the rule to start with:
access_get_door_status is read-only, so it stays allowed. 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_get_door_status call is checked against it from then on.
Questions about access_get_door_status
Get current door lock/position status. It is categorised as a Read tool in the UniFi Access MCP MCP Server, which means it retrieves data without modifying state.
Register the UniFi Access MCP server in PolicyLayer and add a rule for access_get_door_status: 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_get_door_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the access_get_door_status 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_get_door_status. 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_get_door_status 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.
This server
Across the catalogue