move_policy_package_to_folder
A write tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/move-policy-package-to-folder.md
What move_policy_package_to_folder does on Fortimanager
AI agents use move_policy_package_to_folder 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 move_policy_package_to_folder is rated Medium
The tool moves/reorganizes policy packages, which is a reversible modification operation (Write category). Severity is high because misconfiguration or misplacement of security policies could disrupt firewall rule organization and potentially expose or hide critical security controls, affecting network security posture.
From the tool's definition Tool name 'move_policy_package_to_folder' indicates modification of organizational structure within FortiManager; description is empty but sibling tools show this server manages security policies, device configs, and network rules.
Attacks that exploit this kind of access
The rule that runs move_policy_package_to_folder 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 move_policy_package_to_folder, this is the rule to start with:
move_policy_package_to_folder 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 move_policy_package_to_folder call is checked against it from then on.
Questions about move_policy_package_to_folder
move_policy_package_to_folder 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 move_policy_package_to_folder: 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.
move_policy_package_to_folder 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 move_policy_package_to_folder 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 move_policy_package_to_folder. 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.
move_policy_package_to_folder 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