Critical Risk →

delete_ipsec_phase1_interface

delete_ipsec_phase1_interface

How to control delete_ipsec_phase1_interface ↓

What delete_ipsec_phase1_interface does on Fortimanager

AI agents call delete_ipsec_phase1_interface 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_ipsec_phase1_interface needs a policy

The verb 'delete' combined with a network infrastructure object (IPsec Phase 1 interface) indicates irreversible removal of configuration. IPsec Phase 1 is fundamental to VPN tunnel establishment; deleting it would break secure communications and cannot be easily undone without reconfiguration. This is more severe than Write operations.

From the tool's definition Tool name contains 'delete' prefix indicating deletion of 'ipsec_phase1_interface', a critical network security component.

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

How to control delete_ipsec_phase1_interface

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_ipsec_phase1_interface:

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

delete_ipsec_phase1_interface 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_ipsec_phase1_interface

What does the delete_ipsec_phase1_interface tool do? +

delete_ipsec_phase1_interface. 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_ipsec_phase1_interface? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for delete_ipsec_phase1_interface: 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_ipsec_phase1_interface? +

delete_ipsec_phase1_interface 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_ipsec_phase1_interface? +

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

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

delete_ipsec_phase1_interface 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.