get_device_routing_configuration
Get device routing table configuration.
This record as markdown: /tools/jmpijll-fortimanager-mcp/get-device-routing-configuration.md
What get_device_routing_configuration does on Fortimanager
AI agents call get_device_routing_configuration 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 get_device_routing_configuration is rated Low
This tool retrieves network routing configuration from a device, which is a read-only operation with no side effects. While routing configuration information could theoretically inform network topology for attacks, the tool itself merely queries existing data without creating, modifying, or deleting anything. Blast radius is minimal as it only returns information about the current state.
From the tool's definition Tool name and description indicate a retrieval operation: 'Get device routing table configuration' performs a query without modifying state.
Attacks that exploit this kind of access
The rule that runs get_device_routing_configuration 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 get_device_routing_configuration, this is the rule to start with:
get_device_routing_configuration 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 get_device_routing_configuration call is checked against it from then on.
Questions about get_device_routing_configuration
Get device routing table configuration. 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 get_device_routing_configuration: 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.
get_device_routing_configuration 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 get_device_routing_configuration 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 get_device_routing_configuration. 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.
get_device_routing_configuration 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