nvd-search-cves
Search the NVD CVE 2.0 database. Combine any of: keywordSearch (free-text), cpeName (CPE 2.3), cvssV3Severity (NONE|LOW|MEDIUM|HIGH|CRITICAL), pubStartDate/pubEndDate, lastModStartDate/lastModEndDate. Returns up to 2000 results per page; paginate with startIndex.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/nvd-search-cves.md
What nvd-search-cves does on Meta Data Mcp
AI agents call nvd-search-cves to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why nvd-search-cves is rated Low
This tool retrieves and queries publicly available vulnerability data from the National Vulnerability Database. It has no capability to modify, delete, execute code, or trigger external actions—it purely reads and filters existing CVE records. The results are informational only.
From the tool's definition Tool performs search operations on the NVD CVE database using keyword, CPE name, and date filters, returning query results.
Attacks that exploit this kind of access
The rule that runs nvd-search-cves safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nvd-search-cves, this is the rule to start with:
nvd-search-cves is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every nvd-search-cves call is checked against it from then on.
Questions about nvd-search-cves
Search the NVD CVE 2.0 database. Combine any of: keywordSearch (free-text), cpeName (CPE 2.3), cvssV3Severity (NONE|LOW|MEDIUM|HIGH|CRITICAL), pubStartDate/pubEndDate, lastModStartDate/lastModEndDate. Returns up to 2000 results per page; paginate with startIndex. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for nvd-search-cves: 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 Meta Data Mcp. Nothing to install.
nvd-search-cves 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 nvd-search-cves 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 nvd-search-cves. 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.
nvd-search-cves is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue