delete_central_dnat_policy
Delete a central DNAT policy.
This record as markdown: /tools/jmpijll-fortimanager-mcp/delete-central-dnat-policy.md
What delete_central_dnat_policy does on Fortimanager
AI agents call delete_central_dnat_policy 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.
Why delete_central_dnat_policy is rated Critical
Deleting a central DNAT policy is a destructive action that cannot be undone. DNAT (Destination Network Address Translation) policies are critical network configuration rules; their deletion removes firewall rules and network routing logic irreversibly. This has a high blast radius in a FortiManager environment as it could disable network access controls.
From the tool's definition The tool is named 'delete_central_dnat_policy' and its description states 'Delete a central DNAT policy.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_central_dnat_policy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fortimanager, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_central_dnat_policy, this is the rule to start with:
delete_central_dnat_policy 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 Fortimanager, apply this rule, and every delete_central_dnat_policy call is checked against it from then on.
Questions about delete_central_dnat_policy
Delete a central DNAT policy. 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_central_dnat_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 Fortimanager. Nothing to install.
delete_central_dnat_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 delete_central_dnat_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 delete_central_dnat_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.
delete_central_dnat_policy 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.
More on Fortimanager, and thousands of servers like it.
Across the catalogue