clone_package
A write tool on the FortiManager MCP server.
This record as markdown: /tools/rstierli-fortimanager-mcp/clone-package.md
What clone_package does on FortiManager MCP Server
AI agents use clone_package to create or update resources in FortiManager MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FortiManager MCP Server environment.
Why clone_package is rated Medium
The name 'clone_package' suggests creating a copy of an existing policy package, which is a Write operation. On a FortiManager system managing centralized firewall policies, cloning packages could have significant impact if misused (e.g., cloning incorrect configurations at scale). However, the empty description lowers confidence. Severity is high given the firewall policy management context.
From the tool's definition Tool name 'clone_package' on a FortiManager server that handles firewall policy management and device provisioning. Description is empty.
Attacks that exploit this kind of access
The rule that runs clone_package safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FortiManager MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clone_package, this is the rule to start with:
clone_package 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 MCP Server, apply this rule, and every clone_package call is checked against it from then on.
Questions about clone_package
clone_package is a write tool on the FortiManager MCP Server MCP server. It is categorised as a Write tool in the FortiManager MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for clone_package: 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 MCP Server. Nothing to install.
clone_package 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_package 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_package. 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_package is provided by the FortiManager MCP Server MCP server (rstierli/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FortiManager MCP Server, and thousands of servers like it.
This server
Across the catalogue