Get basic information about the network device including hostname,
AI agents call get_device_info 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 retrieves static device metadata (hostname and related basic info) from a Nokia SR Linux network device. It performs a query-like operation with no side effects, reversible modifications, code execution, or destructive actions. The blast radius of misuse is minimal—an agent querying device information cannot harm the system or network. Classification as Read is appropriate.
From the tool's definition Tool name 'get_device_info' and description 'Get basic information about the network device including hostname' indicate a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Get basic information about the network device including hostname,. 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_device_info: 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_device_info 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_info 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_info. 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_info 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 →