DESTRUCTIVE: Delete a DNS policy
AI agents call unifi_delete_dns_policy to permanently remove resources in UniFi Network MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes DNS policies, which cannot be undone. DNS policies govern network traffic filtering and security rules. Deleting a policy is irreversible and could disrupt network operations or security posture. This is a clear Destructive action with high blast radius if invoked incorrectly by an AI agent.
From the tool's definition Tool name contains 'delete' and description explicitly states 'DESTRUCTIVE: Delete a DNS policy'. This irreversibly removes a DNS policy configuration.
Attacks that exploit this kind of access
DESTRUCTIVE: Delete a DNS policy. It is categorised as a Destructive tool in the UniFi Network MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the UniFi Network MCP Server MCP server in PolicyLayer and add a rule for unifi_delete_dns_policy: 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 Network MCP Server. Nothing to install.
unifi_delete_dns_policy 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 unifi_delete_dns_policy 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 unifi_delete_dns_policy. 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.
unifi_delete_dns_policy is provided by the UniFi Network MCP Server MCP server (owine/unifi-network-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →