delete_recurring_schedule
Delete a recurring schedule.
This record as markdown: /tools/jmpijll-fortimanager-mcp/delete-recurring-schedule.md
What delete_recurring_schedule does on Fortimanager
AI agents call delete_recurring_schedule to permanently remove resources in Fortimanager, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_recurring_schedule is rated Critical
The tool permanently deletes a recurring schedule configuration from FortiManager. This is a destructive action that cannot be undone. While the blast radius is limited to schedule objects rather than network-wide impact, the irreversible nature and potential to disrupt automation workflows that depend on the schedule elevates this to high severity.
From the tool's definition Tool name explicitly uses 'delete' and description states 'Delete a recurring schedule' — this is an irreversible data removal operation.
Attacks that exploit this kind of access
The rule that runs delete_recurring_schedule 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 delete_recurring_schedule, this is the rule to start with:
delete_recurring_schedule is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every delete_recurring_schedule call is checked against it from then on.
Questions about delete_recurring_schedule
Delete a recurring schedule. It is categorised as a Destructive tool in the Fortimanager MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fortimanager MCP server in PolicyLayer and add a rule for delete_recurring_schedule: 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.
delete_recurring_schedule is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_recurring_schedule 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 delete_recurring_schedule. 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.
delete_recurring_schedule 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