unifi_unauthorize_guest
Revoke authorization for a guest client by MAC address
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-unauthorize-guest.md
What unifi_unauthorize_guest does on UniFi Access MCP
AI agents call unifi_unauthorize_guest to permanently remove resources in UniFi Access MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why unifi_unauthorize_guest is rated Critical
Revoking guest authorization is a destructive action: it permanently strips access rights and cannot be undone by the tool itself (restoration would require re-authorization through a separate process). The blast radius is high in a physical access control context — an AI agent could lock out legitimate guests or disrupt operations by mass-revoking credentials.
From the tool's definition Tool name contains 'unauthorize' and description states 'Revoke authorization for a guest client' — this is an irreversible removal of access permissions. Once revoked, the guest loses entry credentials that cannot be automatically restored.
Attacks that exploit this kind of access
The rule that runs unifi_unauthorize_guest 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_unauthorize_guest, this is the rule to start with:
unifi_unauthorize_guest is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect UniFi Access MCP, apply this rule, and every unifi_unauthorize_guest call is checked against it from then on.
Questions about unifi_unauthorize_guest
Revoke authorization for a guest client by MAC address. It is categorised as a Destructive tool in the UniFi Access MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the UniFi Access MCP server in PolicyLayer and add a rule for unifi_unauthorize_guest: 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_unauthorize_guest is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the unifi_unauthorize_guest 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_unauthorize_guest. 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_unauthorize_guest 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