New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

install_package

A execute tool on the FortiManager MCP server.

SERVERFortiManager MCP Server SOURCErstierli/fortimanager-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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'

Questions about install_package

What does the install_package tool do? +

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.

How do I enforce a policy on install_package? +

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.

What risk level is install_package? +

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

Can I rate-limit install_package? +

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.

How do I block install_package completely? +

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.

What MCP server provides install_package? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FortiManager MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.