router_static_update
A write tool on the FortiOS 7 6 X MCP server.
This record as markdown: /tools/paoloamato2-fortinet-mcp-server/router-static-update.md
What router_static_update does on FortiOS 7 6 X MCP Server
AI agents use router_static_update to create or update resources in FortiOS 7 6 X MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FortiOS 7 6 X MCP Server environment.
Why router_static_update is rated Medium
This tool updates static route configurations in FortiOS. While the description is empty (lowering confidence slightly), the name unambiguously indicates a Write operation that modifies network routing tables. This is Write rather than Execute because it modifies configuration data rather than executing arbitrary commands.
From the tool's definition Tool name 'router_static_update' indicates modification of router static routing configuration. No description provided, but the 'update' action combined with the 'router_static' resource clearly denotes reversible modification of network routing settings.
Attacks that exploit this kind of access
The rule that runs router_static_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FortiOS 7 6 X MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For router_static_update, this is the rule to start with:
router_static_update 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 FortiOS 7 6 X MCP Server, apply this rule, and every router_static_update call is checked against it from then on.
Questions about router_static_update
router_static_update is a write tool on the FortiOS 7 6 X MCP Server MCP server. It is categorised as a Write tool in the FortiOS 7 6 X MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FortiOS 7 6 X MCP Server MCP server in PolicyLayer and add a rule for router_static_update: 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 FortiOS 7 6 X MCP Server. Nothing to install.
router_static_update 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 router_static_update 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 router_static_update. 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.
router_static_update is provided by the FortiOS 7 6 X MCP Server MCP server (paoloamato2/fortinet-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FortiOS 7 6 X MCP Server, and thousands of servers like it.
This server
Across the catalogue