cve_lookup
AI agents call cve_lookup to retrieve information from CVE Risk MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
CVE lookup is a read-only operation that retrieves and queries existing vulnerability data without modifying, deleting, or executing anything. The blast radius of misuse is minimal—an agent could only access or enumerate CVE information, with no ability to change systems or data. Severity is low because this tool has no side effects beyond information disclosure, which is non-sensitive in a security research context.
From the tool's definition Tool name 'cve_lookup' combined with server purpose of 'CVE lookups and risk assessment' indicates a query/retrieval function. No description provided, but context shows this retrieves vulnerability data from CISA KEV and CVSS databases.
Attacks that exploit this kind of access
cve_lookup. It is categorised as a Read tool in the CVE Risk MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CVE Risk MCP Server MCP server in PolicyLayer and add a rule for cve_lookup: 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 CVE Risk MCP Server. Nothing to install.
cve_lookup 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 cve_lookup 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 cve_lookup. 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.
cve_lookup is provided by the CVE Risk MCP Server MCP server (sarveshkapre/cve-risk-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 →