protect_delete_recording
A destructive tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/protect-delete-recording.md
What protect_delete_recording does on UniFi Access MCP
AI agents call protect_delete_recording 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_recording is rated Critical
The 'delete' verb in the tool name indicates permanent, irreversible removal of recording data. This is destructive even without further context. In a security system managing doors, credentials, and events, recordings are critical audit trails and evidence records. Unauthorized deletion could destroy security footage and compromise compliance/investigation capabilities.
From the tool's definition Tool name 'protect_delete_recording' explicitly contains 'delete', indicating irreversible removal of data (recordings).
Attacks that exploit this kind of access
The rule that runs protect_delete_recording 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_delete_recording, this is the rule to start with:
protect_delete_recording 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 protect_delete_recording call is checked against it from then on.
Questions about protect_delete_recording
protect_delete_recording 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 protect_delete_recording: 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_delete_recording 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 protect_delete_recording 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_delete_recording. 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_delete_recording 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