get_cve_from_nist
AI agents call get_cve_from_nist to retrieve information from Risky Business 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 vulnerability data from a public database (NIST NVD) with no side effects—it is a read-only query operation. Severity is medium rather than low because vulnerability intelligence data could enable attackers to prioritize exploitation targets, though the data itself is already public and widely available. Confidence is reduced from 0.9 to 0.85 due to empty tool description.
From the tool's definition Tool name 'get_cve_from_nist' indicates retrieval of CVE data from NIST NVD; server description confirms 'querying NIST NVD for CVE details' as part of vulnerability research workflows. Tool description is empty, limiting direct confirmation.
Attacks that exploit this kind of access
get_cve_from_nist. It is categorised as a Read tool in the Risky Business MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Risky Business MCP Server MCP server in PolicyLayer and add a rule for get_cve_from_nist: 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 Risky Business MCP Server. Nothing to install.
get_cve_from_nist 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_from_nist 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_from_nist. 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_from_nist is provided by the Risky Business MCP Server MCP server (khizar-anjum/risky-business-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 →