AI agents invoke schedule_policy_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.
Policy installation on network devices is an operational execution action that pushes configuration changes to live infrastructure. The sibling tool 'abort_policy_install' confirms this is an active operation that can be cancelled, indicating it triggers external operations on managed devices.
From the tool's definition Tool name 'schedule_policy_install' and sibling tool 'abort_policy_install' suggest this triggers a policy installation operation on network devices via FortiManager
Documented attack patterns abuse exactly the kind of access schedule_policy_install gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fortimanager, and nothing reaches the server without passing your rules. This is the rule we recommend for schedule_policy_install:
{
"version": "1",
"default": "deny",
"tools": {
"schedule_policy_install": {
"limits": [
{
"counter": "schedule_policy_install_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}schedule_policy_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.
Free to start. No card required.
schedule_policy_install. 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_policy_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_policy_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_policy_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_policy_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_policy_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.
Start from Fortimanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
584 Fortimanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.