protect_alarm_delete_rule
A destructive tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/protect-alarm-delete-rule.md
What protect_alarm_delete_rule does on UniFi Access MCP
AI agents call protect_alarm_delete_rule 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_alarm_delete_rule is rated Critical
The 'delete_rule' operation irreversibly removes alarm protection rules from the system. Even without a description, the 'delete' verb combined with a physical security context (UniFi Access alarm management) indicates a destructive action that cannot be undone. While the empty description lowers confidence slightly, the semantic meaning of 'delete' in a security system is unambiguous.
From the tool's definition Tool name contains 'delete' which indicates irreversible removal of data. The 'protect_alarm' prefix suggests this manages security alarm rules.
Attacks that exploit this kind of access
The rule that runs protect_alarm_delete_rule 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_alarm_delete_rule, this is the rule to start with:
protect_alarm_delete_rule 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_alarm_delete_rule call is checked against it from then on.
Questions about protect_alarm_delete_rule
protect_alarm_delete_rule 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_alarm_delete_rule: 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_alarm_delete_rule 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_alarm_delete_rule 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_alarm_delete_rule. 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_alarm_delete_rule 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