Get the routing table.
AI agents call get_routes to retrieve information from Network MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves network routing table data without side effects. It performs a read-only query of existing system state. There is no capability to modify routes, execute commands, or cause destructive changes. The blast radius of misuse is minimal—an AI agent could only gain visibility into network topology, which does not compromise data integrity or enable unauthorized actions.
From the tool's definition Tool name 'get_routes' and description 'Get the routing table' indicate a data retrieval operation with no modification or execution capability. The action is strictly querying system routing information.
Attacks that exploit this kind of access
Get the routing table. It is categorised as a Read tool in the Network MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Network MCP Server MCP server in PolicyLayer and add a rule for get_routes: 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 Network MCP Server. Nothing to install.
get_routes 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_routes 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_routes. 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_routes is provided by the Network MCP Server MCP server (labeveryday/network-mcp). 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 →