install_package_to_device_db
A execute tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/install-package-to-device-db.md
What install_package_to_device_db does on Fortimanager
AI agents invoke install_package_to_device_db to trigger actions in Fortimanager. 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_to_device_db is rated High
The name suggests installing a policy package to a device database in FortiManager, which is an operational action that pushes configuration changes to devices. This is likely an Execute-level action as it triggers external operations on network devices. However, the empty description significantly lowers confidence.
From the tool's definition Tool name: install_package_to_device_db; description is empty
Attacks that exploit this kind of access
The rule that runs install_package_to_device_db 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 install_package_to_device_db, this is the rule to start with:
install_package_to_device_db 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, apply this rule, and every install_package_to_device_db call is checked against it from then on.
Questions about install_package_to_device_db
install_package_to_device_db is a execute tool on the Fortimanager MCP server. It is categorised as a Execute tool in the Fortimanager MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fortimanager MCP server in PolicyLayer and add a rule for install_package_to_device_db: 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.
install_package_to_device_db 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_to_device_db 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_to_device_db. 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_to_device_db 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.
Across the catalogue