access_delete_visitor
A destructive tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/access-delete-visitor.md
What access_delete_visitor does on UniFi Access MCP
AI agents call access_delete_visitor 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 access_delete_visitor is rated Critical
The tool performs deletion of visitor records in an access control system, which is an irreversible operation that cannot be undone. While the description is empty, the name unambiguously indicates destructive functionality. Severity is high because deleting visitors could disrupt legitimate access, affect auditing trails, or be misused to cover tracks.
From the tool's definition Tool name 'access_delete_visitor' indicates permanent deletion of visitor records. The 'delete' verb combined with 'visitor' (a credential/access entity) in a UniFi Access control system implies irreversible removal of access-related data.
Attacks that exploit this kind of access
The rule that runs access_delete_visitor 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_delete_visitor, this is the rule to start with:
access_delete_visitor 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 access_delete_visitor call is checked against it from then on.
Questions about access_delete_visitor
access_delete_visitor is a destructive tool on the UniFi Access MCP server. 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 access_delete_visitor: 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_delete_visitor 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 access_delete_visitor 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_delete_visitor. 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_delete_visitor 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