router_static_list

List all IPv4 static routes.

SERVERFortiOS 7 6 X MCP Server SOURCEpaoloamato2/fortinet-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/paoloamato2-fortinet-mcp-server/router-static-list.md

WHAT IT DOES

What router_static_list does on FortiOS 7 6 X MCP Server

AI agents call router_static_list to retrieve information from FortiOS 7 6 X MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why router_static_list is rated Low

This tool queries and returns existing static route configuration data without creating, modifying, deleting, or executing any operations. It is a read-only informational retrieval function. The blast radius of misuse is low since listing routes cannot harm system state or cause unintended effects beyond information disclosure.

From the tool's definition Tool name contains 'list' and description states 'List all IPv4 static routes' — a retrieval operation with no modifications or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs router_static_list 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_list, this is the rule to start with:

router_static_list Allowed

router_static_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "router_static_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FortiOS 7 6 X MCP Server, apply this rule, and every router_static_list call is checked against it from then on.

FAQ

Questions about router_static_list

What does the router_static_list tool do? +

List all IPv4 static routes. It is categorised as a Read tool in the FortiOS 7 6 X MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on router_static_list? +

Register the FortiOS 7 6 X MCP Server MCP server in PolicyLayer and add a rule for router_static_list: 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.

What risk level is router_static_list? +

router_static_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit router_static_list? +

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

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

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

KEEP EXPLORING

More on FortiOS 7 6 X MCP Server, and thousands of servers like it.

This server

All 240 FortiOS 7 6 X MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →