create_ipsec_phase2_interface
A write tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/create-ipsec-phase2-interface.md
What create_ipsec_phase2_interface does on Fortimanager
AI agents use create_ipsec_phase2_interface to create or update resources in Fortimanager, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fortimanager environment.
Why create_ipsec_phase2_interface is rated Medium
This tool creates IPsec Phase 2 interface configurations, which is a reversible write operation on FortiManager's security infrastructure. While IPsec configuration could have downstream effects on network traffic, the tool itself performs data creation/modification rather than deletion (Destructive), code execution (Execute), or financial transactions (Financial).
From the tool's definition Tool name 'create_ipsec_phase2_interface' indicates creation of IPsec Phase 2 configuration. The tool prefix 'create_' combined with sibling tools like 'add_custom_command_to_template', 'add_device_to_group', and 'add_ips_rule' shows this server creates and…
Attacks that exploit this kind of access
The rule that runs create_ipsec_phase2_interface 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 create_ipsec_phase2_interface, this is the rule to start with:
create_ipsec_phase2_interface stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every create_ipsec_phase2_interface call is checked against it from then on.
Questions about create_ipsec_phase2_interface
create_ipsec_phase2_interface is a write tool on the Fortimanager MCP server. It is categorised as a Write tool in the Fortimanager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fortimanager MCP server in PolicyLayer and add a rule for create_ipsec_phase2_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.
create_ipsec_phase2_interface is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_ipsec_phase2_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.
Set action: deny in the PolicyLayer policy for create_ipsec_phase2_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.
create_ipsec_phase2_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.
More on Fortimanager, and thousands of servers like it.
This server
Across the catalogue