Search for vulnerabilities affecting specific products or CPEs. Supports filtering by KEV status, sorting by EPSS score, date ranges, and pagination. Can search by product name or CPE 2.3 identifier. Returns detailed vulnerability information including severity scores and impact assessments.
AI agents call cves_by_product to retrieve information from Mcp Shodan without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries vulnerability information from the Shodan CVEDB and returns results. While the information retrieved could be sensitive (vulnerability data), the tool itself has no side effects—it does not execute code, modify data, delete records, or trigger external operations. It is a pure read operation that retrieves and displays existing vulnerability records.
From the tool's definition Tool performs vulnerability searches and returns 'detailed vulnerability information including severity scores and impact assessments' with no mention of modifying, executing, or deleting data. The verb 'search' and 'returns' indicate data retrieval only.
Attacks that exploit this kind of access
Search for vulnerabilities affecting specific products or CPEs. Supports filtering by KEV status, sorting by EPSS score, date ranges, and pagination. Can search by product name or CPE 2.3 identifier. Returns detailed vulnerability information including severity scores and impact assessments. It is categorised as a Read tool in the Mcp Shodan MCP Server, which means it retrieves data without modifying state.
Register the Mcp Shodan MCP server in PolicyLayer and add a rule for cves_by_product: 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 Mcp Shodan. Nothing to install.
cves_by_product 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 cves_by_product 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 cves_by_product. 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.
cves_by_product is provided by the Mcp Shodan MCP server (w0h1v/mcp-shodan). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.