execute_script_on_package · FortiManager MCP Server MCP

WHAT IT DOES

What execute_script_on_package does on FortiManager MCP Server

AI agents invoke execute_script_on_package to trigger actions in FortiManager MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_script_on_package needs a policy

The tool name explicitly contains 'execute_script', which denotes running code/commands. In a FortiManager context managing centralized firewall policies and device configurations, script execution on a package (a collection of firewall policies/configurations) could affect multiple devices and network rules.

From the tool's definition Tool name 'execute_script_on_package' indicates execution of scripts; FortiManager context involves network firewall policy and device provisioning where script execution can trigger substantial side effects across managed devices.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_script_on_package Rate-limited

execute_script_on_package stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_script_on_package": {
      "limits": [
        {
          "counter": "execute_script_on_package_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 execute_script_on_package

What does the execute_script_on_package tool do? +

execute_script_on_package. It is categorised as a Execute tool in the FortiManager MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_script_on_package? +

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

What risk level is execute_script_on_package? +

execute_script_on_package is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_script_on_package? +

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

How do I block execute_script_on_package completely? +

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

What MCP server provides execute_script_on_package? +

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