Low Risk

router_static_get

router_static_get

How to control router_static_get ↓

What router_static_get does on FortiOS 7 6 X MCP Server

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

Low Risk

Why router_static_get needs a policy

The 'get' verb and context of querying static router configuration from a FortiOS API indicates this retrieves data about existing router static routes without modifying them. No side effects or state changes are implied. Blast radius is minimal—read access to network routing configuration poses low risk unless combined with other tools for reconnaissance.

From the tool's definition Tool name 'router_static_get' indicates a retrieval operation (get suffix). No description provided, but follows the naming pattern of sibling tools like 'antivirus_profile_get', 'antivirus_settings_get', 'certificate_ca_list' which are read operations.

Documented attack patterns abuse exactly the kind of access router_static_get gives an agent:

How to control router_static_get

PolicyLayer is an MCP gateway — it sits between your AI agents and FortiOS 7 6 X MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for router_static_get:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "router_static_get": {}
  }
}

router_static_get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register FortiOS 7 6 X MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about router_static_get

What does the router_static_get tool do? +

router_static_get. 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_get? +

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

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

Can I rate-limit router_static_get? +

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

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

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

Enforce policy on every FortiOS 7 6 X MCP Server tool call.

Start from FortiOS 7 6 X MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

240 FortiOS 7 6 X MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.