Retrieve information about a specific CVE ID from cvedb.shodan.io
AI agents call cvedb_info 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 existing CVE vulnerability metadata from a public database without creating, modifying, deleting, or executing any operations. It is purely informational and poses minimal risk even if misused by an AI agent, as it only returns publicly available security data.
From the tool's definition Tool name 'cvedb_info' and description 'Retrieve information about a specific CVE ID' indicate a query-only operation with no side effects. The verb 'retrieve' and context of accessing CVE database information confirm read-only functionality.
Attacks that exploit this kind of access
Retrieve information about a specific CVE ID from cvedb.shodan.io. 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 cvedb_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 Shodan-MCP-Server. Nothing to install.
cvedb_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 cvedb_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 cvedb_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.
cvedb_info 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 →