Search Shodan for devices matching a query
AI agents call search to retrieve information from Shodan-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 information from the Shodan database about internet-connected devices, vulnerabilities, and configurations. While it is fundamentally a Read operation with no direct side effects, the severity is elevated to 'medium' because the information returned (device locations, open ports, software versions, vulnerabilities) could be used for reconnaissance, identification of targets for attacks, or to…
From the tool's definition Tool name 'search' and description 'Search Shodan for devices matching a query' indicate data retrieval without modification. The Shodan API context confirms this is a query operation that retrieves information about devices and their properties.
Attacks that exploit this kind of access
Search Shodan for devices matching a query. It is categorised as a Read tool in the Shodan-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the Shodan-MCP-Server MCP server in PolicyLayer and add a rule for search: 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 Shodan-MCP-Server. Nothing to install.
search 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 search 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 search. 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.
search is provided by the Shodan-MCP-Server MCP server (x3r0k/shodan-mcp-server-inspector). 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 →