unassign_static_route_template
A write tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/unassign-static-route-template.md
What unassign_static_route_template does on Fortimanager
AI agents use unassign_static_route_template to create or update resources in Fortimanager, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fortimanager environment.
Why unassign_static_route_template is rated Medium
Based on the name alone, this tool likely removes an assignment of a static route template from a device or group, which is a reversible configuration change (Write). However, since the description is empty, confidence is reduced.
From the tool's definition Tool name: 'unassign_static_route_template' — description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs unassign_static_route_template 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 unassign_static_route_template, this is the rule to start with:
unassign_static_route_template stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 unassign_static_route_template call is checked against it from then on.
Questions about unassign_static_route_template
unassign_static_route_template is a write tool on the Fortimanager MCP server. It is categorised as a Write tool in the Fortimanager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fortimanager MCP server in PolicyLayer and add a rule for unassign_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.
unassign_static_route_template is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unassign_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.
Set action: deny in the PolicyLayer policy for unassign_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.
unassign_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.
This server
Across the catalogue