delete_static_route_template

Delete a static route template.

SERVERFortimanager SOURCEjmpijll/fortimanager-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jmpijll-fortimanager-mcp/delete-static-route-template.md

What delete_static_route_template does on Fortimanager

AI agents call delete_static_route_template 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_static_route_template is rated Critical

This tool permanently removes a static route template from FortiManager configuration. Deletion of network routing templates is irreversible and could disrupt network traffic flows if the template is in use or referenced by other configurations. The blast radius is high because misconfigured deletion could affect multiple devices or policies that depend on the template.

From the tool's definition Tool name 'delete_static_route_template' explicitly performs a delete operation on a static route template, which is an irreversible action. The verb 'delete' is characteristic of destructive operations that cannot be undone.

Questions about delete_static_route_template

What does the delete_static_route_template tool do? +

Delete a static route template. 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.

How do I enforce a policy on delete_static_route_template? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for delete_static_route_template: 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.

What risk level is delete_static_route_template? +

delete_static_route_template is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_static_route_template? +

Yes. Add a rate_limit block to the delete_static_route_template 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 delete_static_route_template completely? +

Set action: deny in the PolicyLayer policy for delete_static_route_template. 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 delete_static_route_template? +

delete_static_route_template 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.

// 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'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.