list_static_route_templates
A read tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/list-static-route-templates.md
What list_static_route_templates does on Fortimanager
AI agents call list_static_route_templates to retrieve information from Fortimanager without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_static_route_templates is rated Low
The 'list_' prefix strongly indicates a read-only operation that queries and returns static route templates from FortiManager. Even if misused by an agent, listing configuration templates poses minimal risk—no data is deleted, modified, or executed. The empty description reduces confidence slightly, but the naming convention is clear.
From the tool's definition Tool name 'list_static_route_templates' uses the 'list' verb, which retrieves and enumerates data without modification. The description is empty, but the name pattern is consistent with query operations.
Attacks that exploit this kind of access
The rule that runs list_static_route_templates 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 list_static_route_templates, this is the rule to start with:
list_static_route_templates is read-only, so it stays allowed. 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 list_static_route_templates call is checked against it from then on.
Questions about list_static_route_templates
list_static_route_templates is a read tool on the Fortimanager MCP server. It is categorised as a Read tool in the Fortimanager MCP Server, which means it retrieves data without modifying state.
Register the Fortimanager MCP server in PolicyLayer and add a rule for list_static_route_templates: 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.
list_static_route_templates is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_static_route_templates 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 list_static_route_templates. 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.
list_static_route_templates 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