AI agents call search_cve_by_keyword to retrieve information from Nvd Cve without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves CVE vulnerability data based on keyword search parameters. It has no side effects, does not modify data, execute code, or trigger external operations. It is purely informational retrieval, making it a Read category tool with low severity risk.
From the tool's definition Tool description states it 'Search[es] CVEs' and retrieves data from the NVD API. No modification, deletion, or execution capabilities are described.
Attacks that exploit this kind of access
Search CVEs by product name or any keyword. Optionally limit to the last days_back days (max 120). It is categorised as a Read tool in the Nvd Cve MCP Server, which means it retrieves data without modifying state.
Register the Nvd Cve MCP server in PolicyLayer and add a rule for search_cve_by_keyword: 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 Nvd Cve. Nothing to install.
search_cve_by_keyword 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 search_cve_by_keyword 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 search_cve_by_keyword. 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.
search_cve_by_keyword is provided by the Nvd Cve MCP server (millsks/nvd-cve-mcp-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 →