protect_alarm_delete_rule

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

Questions about protect_alarm_delete_rule

What does the protect_alarm_delete_rule tool do? +

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.

How do I enforce a policy on protect_alarm_delete_rule? +

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.

What risk level is protect_alarm_delete_rule? +

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.

Can I rate-limit protect_alarm_delete_rule? +

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.

How do I block protect_alarm_delete_rule completely? +

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.

What MCP server provides protect_alarm_delete_rule? +

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.

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