protect_merge_known_faces
A write tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/protect-merge-known-faces.md
What protect_merge_known_faces does on UniFi Access MCP
AI agents use protect_merge_known_faces to create or update resources in UniFi Access MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UniFi Access MCP environment.
Why protect_merge_known_faces is rated Medium
This tool appears to modify face recognition data used by the access control system. While not irreversible (Write rather than Destructive) and not executing arbitrary code (Execute), merging facial biometric records could alter how the system recognizes and grants access to individuals.
From the tool's definition Tool name 'protect_merge_known_faces' suggests modifying or consolidating face recognition data. The description is empty, making definitive classification difficult.
Attacks that exploit this kind of access
The rule that runs protect_merge_known_faces 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 protect_merge_known_faces, this is the rule to start with:
protect_merge_known_faces stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 protect_merge_known_faces call is checked against it from then on.
Questions about protect_merge_known_faces
protect_merge_known_faces is a write tool on the UniFi Access MCP server. It is categorised as a Write tool in the UniFi Access MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the UniFi Access MCP server in PolicyLayer and add a rule for protect_merge_known_faces: 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.
protect_merge_known_faces is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the protect_merge_known_faces 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 protect_merge_known_faces. 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.
protect_merge_known_faces 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