insert_policy_at_position
A write tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/insert-policy-at-position.md
What insert_policy_at_position does on Fortimanager
AI agents use insert_policy_at_position 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 insert_policy_at_position is rated Medium
Inserting a policy modifies the firewall rule order and active security configuration, which is a reversible Write operation. This is not merely reading (no 'get'/'list'/'query' pattern), not destructive (insertion can be undone by removal), and not Execute in the arbitrary-code sense.
From the tool's definition Tool name 'insert_policy_at_position' indicates creation/insertion of a security policy at a specified location in a policy list.
Attacks that exploit this kind of access
The rule that runs insert_policy_at_position 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 insert_policy_at_position, this is the rule to start with:
insert_policy_at_position 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 insert_policy_at_position call is checked against it from then on.
Questions about insert_policy_at_position
insert_policy_at_position 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 insert_policy_at_position: 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.
insert_policy_at_position 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 insert_policy_at_position 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 insert_policy_at_position. 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.
insert_policy_at_position 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