clone_firewall_policy
A write tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/clone-firewall-policy.md
What clone_firewall_policy does on Fortimanager
AI agents use clone_firewall_policy 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 clone_firewall_policy is rated Medium
Cloning a firewall policy typically creates a new policy entry based on an existing one, which is a Write operation (reversible creation). However, the empty description lowers confidence. Given sibling tools involve policy management and network configuration, misuse could have high blast radius by introducing duplicate or misconfigured firewall policies affecting network security posture.
From the tool's definition Tool name 'clone_firewall_policy' suggests duplicating an existing firewall policy; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs clone_firewall_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 clone_firewall_policy, this is the rule to start with:
clone_firewall_policy 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 clone_firewall_policy call is checked against it from then on.
Questions about clone_firewall_policy
clone_firewall_policy 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 clone_firewall_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.
clone_firewall_policy 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 clone_firewall_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 clone_firewall_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.
clone_firewall_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.
This server
Across the catalogue