Critical Risk →

delete_dns_record

Delete a DNS record from a domain you own. Costs $0.10 USDC. IMPORTANT: Always delete DNS records one at a time (sequentially, not in parallel).

Part of the Bloomfilter MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@bloomfilter/mcp-server Destructive Risk 4/5

AI agents may call delete_dns_record to permanently remove or destroy resources in Bloomfilter. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call delete_dns_record in a loop, permanently destroying resources in Bloomfilter. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-eronmmer-bloomfilter.yaml
tools:
  delete_dns_record:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Bloomfilter policy for all 10 tools.

Tool Name delete_dns_record
Category Destructive
Risk Level Critical

View all 10 tools →

Agents calling destructive-class tools like delete_dns_record have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

delete_dns_record is one of the critical-risk operations in Bloomfilter. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the delete_dns_record tool do? +

Delete a DNS record from a domain you own. Costs $0.10 USDC. IMPORTANT: Always delete DNS records one at a time (sequentially, not in parallel).. It is categorised as a Destructive tool in the Bloomfilter 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 delete_dns_record? +

Add a rule in your Intercept YAML policy under the tools section for delete_dns_record. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Bloomfilter MCP server.

What risk level is delete_dns_record? +

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.

Can I rate-limit delete_dns_record? +

Yes. Add a rate_limit block to the delete_dns_record rule in your Intercept 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 delete_dns_record completely? +

Set action: deny in the Intercept policy for 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.

What MCP server provides delete_dns_record? +

delete_dns_record is provided by the Bloomfilter MCP server (@bloomfilter/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Bloomfilter

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.