schedule_package_install
Schedule a policy package installation for future time.
This record as markdown: /tools/jmpijll-fortimanager-mcp/schedule-package-install.md
What schedule_package_install does on Fortimanager
AI agents invoke schedule_package_install 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 schedule_package_install is rated High
This tool triggers an external operation (policy package installation) on network infrastructure (FortiManager), which can alter firewall policies and network security configurations. While it schedules for a future time, it commits and initiates a real change to live network devices.
From the tool's definition Schedule a policy package installation for future time
Attacks that exploit this kind of access
The rule that runs schedule_package_install 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 schedule_package_install, this is the rule to start with:
schedule_package_install 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 schedule_package_install call is checked against it from then on.
Questions about schedule_package_install
Schedule a policy package installation for future time. 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 schedule_package_install: 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.
schedule_package_install 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 schedule_package_install 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 schedule_package_install. 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.
schedule_package_install 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