protect_delete_known_face

A destructive tool on the UniFi Access MCP server.

SERVERUniFi Access MCP SOURCEpypi:unifi-protect-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/protect-delete-known-face.md

What protect_delete_known_face does on UniFi Access MCP

AI agents call protect_delete_known_face 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 protect_delete_known_face is rated Critical

The tool deletes a known face from what appears to be a biometric database used for access control. This is irreversible and cannot be undone without re-enrollment. While not as severe as deleting all access records, it materially alters a security system's state. Destructive takes precedence over Write (which implies reversibility) and exceeds Execute (which may have reversible side effects).

From the tool's definition Tool name 'protect_delete_known_face' contains the verb 'delete', which indicates irreversible removal of data (a facial recognition profile or biometric record). The empty description prevents full certainty but the action is clearly destructive.

Questions about protect_delete_known_face

What does the protect_delete_known_face tool do? +

protect_delete_known_face 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.

How do I enforce a policy on protect_delete_known_face? +

Register the UniFi Access MCP server in PolicyLayer and add a rule for protect_delete_known_face: 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.

What risk level is protect_delete_known_face? +

protect_delete_known_face is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit protect_delete_known_face? +

Yes. Add a rate_limit block to the protect_delete_known_face 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.

How do I block protect_delete_known_face completely? +

Set action: deny in the PolicyLayer policy for protect_delete_known_face. 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.

What MCP server provides protect_delete_known_face? +

protect_delete_known_face 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of UniFi Access's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.