install_package
A execute tool on the FortiManager MCP server.
This record as markdown: /tools/rstierli-fortimanager-mcp/install-package.md
What install_package does on FortiManager MCP Server
AI agents invoke install_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 install_package is rated High
Installing a package on FortiManager typically means pushing/deploying firewall policy packages to managed devices, which triggers external operations that reconfigure live network security infrastructure. This is an Execute-level action with critical severity since misconfiguration could expose or block network traffic across all managed firewalls.
From the tool's definition Tool name 'install_package' on a FortiManager server that handles 'centralized firewall policy management, device provisioning, and network configuration'
Attacks that exploit this kind of access
The rule that runs install_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 install_package, this is the rule to start with:
install_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.
The button opens the PolicyLayer dashboard: create your workspace, connect FortiManager MCP Server, apply this rule, and every install_package call is checked against it from then on.
Questions about install_package
install_package is a execute tool on the FortiManager MCP Server MCP server. 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.
Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for install_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.
install_package is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the install_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 install_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.
install_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.
Across the catalogue