Show the routing table of the network device.
AI agents call get_routes to retrieve information from sheridan Lab Jack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves network routing information from a Nokia SR Linux device without modifying any state. It is a passive information retrieval operation analogous to running 'show ip route' on a network device. There are no destructive, financial, or execution risks—it simply returns data about existing routes. Low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_routes' and description 'Show the routing table of the network device' indicate a retrieval operation with no side effects. The verb 'show' and action of displaying a routing table are read-only operations.
Attacks that exploit this kind of access
Show the routing table of the network device. It is categorised as a Read tool in the sheridan Lab Jack MCP Server, which means it retrieves data without modifying state.
Register the sheridan Lab Jack 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 sheridan Lab Jack. 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 sheridan Lab Jack MCP server (jackg27/sheridan-lab-jack). 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 →