move_firewall_policy · FortiManager MCP Server MCP

WHAT IT DOES

What move_firewall_policy does on FortiManager MCP Server

AI agents use move_firewall_policy 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 IT NEEDS A POLICY

Why move_firewall_policy needs a policy

The name suggests reordering or relocating a firewall policy within a policy package. Moving a policy changes its position/order in the ruleset, which is a reversible write operation but carries high severity since firewall policy ordering directly impacts network security posture. Description is empty, lowering confidence.

From the tool's definition Tool name 'move_firewall_policy' on a FortiManager server for firewall policy management. Description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_firewall_policy Rate-limited

move_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_firewall_policy": {
      "limits": [
        {
          "counter": "move_firewall_policy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches FortiManager MCP Server, so you can run agents against it safely.

FAQ

Questions about move_firewall_policy

What does the move_firewall_policy tool do? +

move_firewall_policy. 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.

How do I enforce a policy on move_firewall_policy? +

Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for move_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 MCP Server. Nothing to install.

What risk level is move_firewall_policy? +

move_firewall_policy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit move_firewall_policy? +

Yes. Add a rate_limit block to the move_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.

How do I block move_firewall_policy completely? +

Set action: deny in the PolicyLayer policy for move_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.

What MCP server provides move_firewall_policy? +

move_firewall_policy 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.