Get full details of a specific vulnerability by its CVE ID (e.g.
AI agents call get_vulnerability to retrieve information from Vulnerability Registry 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 and returns vulnerability information based on a CVE ID lookup. It has no side effects, does not modify data, does not execute code or commands, and does not involve financial transactions. It is a pure read operation typical of a database query tool. The low severity reflects minimal risk even if misused, as it only exposes already-public vulnerability metadata.
From the tool's definition Tool name is 'get_vulnerability' and description states 'Get full details of a specific vulnerability by its CVE ID' - this is a retrieval operation that queries vulnerability data without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
Get full details of a specific vulnerability by its CVE ID (e.g. It is categorised as a Read tool in the Vulnerability Registry MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vulnerability Registry MCP Server MCP server in PolicyLayer and add a rule for get_vulnerability: 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 Vulnerability Registry MCP Server. Nothing to install.
get_vulnerability 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_vulnerability 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_vulnerability. 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_vulnerability is provided by the Vulnerability Registry MCP Server MCP server (orcohen5/vulnerability-registry). 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 →