import_policy_configuration
A write tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/import-policy-configuration.md
What import_policy_configuration does on Fortimanager
AI agents use import_policy_configuration 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 import_policy_configuration is rated Medium
Import operations typically create or update configurations in network security appliances. Given that the description is empty, classification relies on the tool name and server context. This is a Write rather than Execute operation because it appears to be a data import/creation function rather than arbitrary command execution.
From the tool's definition Tool name 'import_policy_configuration' indicates creation or modification of policy data. Sibling tools on the same server include 'add_policies_to_block', 'add_custom_command_to_template', and 'add_device_to_group', which are all Write operations.
Attacks that exploit this kind of access
The rule that runs import_policy_configuration 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 import_policy_configuration, this is the rule to start with:
import_policy_configuration 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 import_policy_configuration call is checked against it from then on.
Questions about import_policy_configuration
import_policy_configuration 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 import_policy_configuration: 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.
import_policy_configuration 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 import_policy_configuration 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 import_policy_configuration. 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.
import_policy_configuration 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