Get full device history including first seen, last seen, and visit counts.
AI agents call get_device_history to retrieve information from Network Scanner MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical information about network devices without side effects. It falls squarely into the Read category. Severity is elevated to medium (rather than low) because device history can reveal infrastructure patterns, usage habits, and network topology details that could inform reconnaissance for targeted attacks, especially given the server's design for 'autonomous AI systems.' The historical…
From the tool's definition Tool retrieves historical metadata about devices: 'Get full device history including first seen, last seen, and visit counts.' No modification, deletion, or external execution occurs. Pure data retrieval.
Attacks that exploit this kind of access
Get full device history including first seen, last seen, and visit counts. It is categorised as a Read tool in the Network Scanner MCP MCP Server, which means it retrieves data without modifying state.
Register the Network Scanner MCP server in PolicyLayer and add a rule for get_device_history: 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 Scanner MCP. Nothing to install.
get_device_history 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_history 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_history. 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_history is provided by the Network Scanner MCP server (marc-shade/network-scanner-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 →