Fetch CVE data from the NVD API.
AI agents call get_cve_data to retrieve information from MCP Developer Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a GET/query operation against a public database (NVD API) to retrieve vulnerability information. There are no data modifications, destructive actions, code execution, or financial implications. The action is purely informational retrieval, making it a Read category tool.
From the tool's definition Tool description states "Fetch CVE data from the NVD API" - the verb "Fetch" indicates data retrieval. CVE (Common Vulnerabilities and Exposures) data from NVD (National Vulnerability Database) is public, read-only information with no side effects on systems…
Attacks that exploit this kind of access
Fetch CVE data from the NVD API. It is categorised as a Read tool in the MCP Developer Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Developer Server MCP server in PolicyLayer and add a rule for get_cve_data: 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 Developer Server. Nothing to install.
get_cve_data 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_cve_data 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_cve_data. 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_cve_data is provided by the MCP Developer Server MCP server (ra86-dev/mcpdev-server). 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 →