AI agents call delete_firewall_zone 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.
Deletion of firewall zones is irreversible and impacts network security posture. Without a description, we rely on the function name; 'delete' clearly maps to the Destructive category. The blast radius is high because misconfigured or malicious deletion of firewall zones could disrupt network segmentation and expose systems.
From the tool's definition Tool named 'delete_firewall_zone' with no description provided. The 'delete' verb combined with 'firewall_zone' (a network security configuration element) indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_firewall_zone gives an agent:
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_firewall_zone:
{
"version": "1",
"default": "deny",
"hide": [
"delete_firewall_zone"
]
}delete_firewall_zone disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_firewall_zone. 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.
Register the Fortimanager MCP server in PolicyLayer and add a rule for delete_firewall_zone: 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.
delete_firewall_zone 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 delete_firewall_zone 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 delete_firewall_zone. 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.
delete_firewall_zone 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.
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.