unifi_delete_dns_record
Delete a static DNS record. Use unifi_list_dns_records to find record IDs. Requires confirmation.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/unifi-delete-dns-record.md
What unifi_delete_dns_record does on UniFi Access MCP
AI agents call unifi_delete_dns_record 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 unifi_delete_dns_record is rated Critical
The tool deletes DNS records, which is an irreversible action. Even though it requires confirmation, deletion of DNS records can disrupt network services and cannot be undone without manual recreation. This fits the Destructive category as it permanently removes data. Severity is high because misconfiguration or malicious deletion of DNS records could interrupt critical services for an organization's network.
From the tool's definition Tool name includes 'delete' and description states 'Delete a static DNS record.' This is an irreversible operation that removes DNS configuration.
Attacks that exploit this kind of access
The rule that runs unifi_delete_dns_record 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 unifi_delete_dns_record, this is the rule to start with:
unifi_delete_dns_record 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 unifi_delete_dns_record call is checked against it from then on.
Questions about unifi_delete_dns_record
Delete a static DNS record. Use unifi_list_dns_records to find record IDs. Requires confirmation. 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 unifi_delete_dns_record: 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.
unifi_delete_dns_record 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_record 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_record. 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_record 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