Critical Risk →

delete_dns_filter_domain

Delete a DNS filter domain list.

How to control delete_dns_filter_domain ↓

What delete_dns_filter_domain does on Fortimanager

AI agents call delete_dns_filter_domain to permanently remove resources in Fortimanager — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_dns_filter_domain needs a policy

This tool permanently removes DNS filter domain list entries from FortiManager configuration. Deletion is irreversible and could disrupt security policies if misused by an AI agent, causing loss of firewall filtering rules. This constitutes a Destructive action, which takes precedence over Write due to its irreversible nature.

From the tool's definition Tool name contains 'delete' and description states 'Delete a DNS filter domain list', indicating irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_dns_filter_domain gives an agent:

How to control delete_dns_filter_domain

PolicyLayer is an MCP gateway — it sits between your AI agents and Fortimanager, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_dns_filter_domain:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_dns_filter_domain"
  ]
}

delete_dns_filter_domain disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Fortimanager — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_dns_filter_domain

What does the delete_dns_filter_domain tool do? +

Delete a DNS filter domain list. It is categorised as a Destructive tool in the Fortimanager 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_filter_domain? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for delete_dns_filter_domain: 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 Fortimanager. Nothing to install.

What risk level is delete_dns_filter_domain? +

delete_dns_filter_domain 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_filter_domain? +

Yes. Add a rate_limit block to the delete_dns_filter_domain 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 delete_dns_filter_domain completely? +

Set action: deny in the PolicyLayer policy for delete_dns_filter_domain. 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_filter_domain? +

delete_dns_filter_domain is provided by the Fortimanager MCP server (jmpijll/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fortimanager tool call.

Start from Fortimanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

584 Fortimanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.