fortigate_lookup_route_for_ip
AI agents call fortigate_lookup_route_for_ip to retrieve information from Fortigate MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves routing information for an IP address without modifying state. It is a diagnostic query operation consistent with the server's read-only security analysis mandate. No data creation, modification, deletion, code execution, or financial impact is possible. The empty description is compensated by strong contextual evidence from the server's stated purpose and sibling tools.
From the tool's definition Tool name 'fortigate_lookup_route_for_ip' indicates a lookup/query operation. Server description explicitly states 'read-only querying and diagnostics' and all sibling tools (fortigate_compare_snapshots, fortigate_export_readonly_snapshot,…
Attacks that exploit this kind of access
fortigate_lookup_route_for_ip. It is categorised as a Read tool in the Fortigate MCP MCP Server, which means it retrieves data without modifying state.
Register the Fortigate MCP server in PolicyLayer and add a rule for fortigate_lookup_route_for_ip: 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 Fortigate MCP. Nothing to install.
fortigate_lookup_route_for_ip 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 fortigate_lookup_route_for_ip 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 fortigate_lookup_route_for_ip. 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.
fortigate_lookup_route_for_ip is provided by the Fortigate MCP server (picaresco/mcp-fortigate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →