security_fetch_cve_detail
Fetch full detail for a specific CVE by ID. Read-only. No side effects. Idempotent. cve_id: CVE identifier in format CVE-YYYY-NNNNN e.g. CVE-2021-44228. Required. Returns description, CVSS base score, affected products, patch references, and publish date. Use this when you have a CVE ID and need ...
This record as markdown: /tools/dev-7bd0-mcp-server/security-fetch-cve-detail.md
What security_fetch_cve_detail does on DataNexus MCP
AI agents call security_fetch_cve_detail to retrieve information from DataNexus MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
cve_id | string | — | CVE identifier e.g. CVE-2021-44228. Required. |
Parameters from the server's own tool schema.
Why security_fetch_cve_detail is rated Low
This tool purely retrieves information about known vulnerabilities (CVE details) from a public, verified data source. It has no side effects, cannot modify data, and does not execute code or commands. The blast radius of misuse is minimal—an agent could only consume data or make excessive read requests. This is a straightforward Read category tool.
From the tool's definition Tool description explicitly states "Read-only. No side effects. Idempotent." It fetches and retrieves CVE vulnerability details from NIST NVD without modifying any data or triggering external operations.
Attacks that exploit this kind of access
The rule that runs security_fetch_cve_detail safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For security_fetch_cve_detail, this is the rule to start with:
security_fetch_cve_detail 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 DataNexus MCP, apply this rule, and every security_fetch_cve_detail call is checked against it from then on.
Questions about security_fetch_cve_detail
Fetch full detail for a specific CVE by ID. Read-only. No side effects. Idempotent. cve_id: CVE identifier in format CVE-YYYY-NNNNN e.g. CVE-2021-44228. Required. Returns description, CVSS base score, affected products, patch references, and publish date. Use this when you have a CVE ID and need complete detail beyond what a package scan returns. Use security_fetch_package_vulnerabilities instead when you want all CVEs for a package version. Verified source: NIST NVD. 1-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_fetch_cve_detail", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}". It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.
security_fetch_cve_detail accepts 1 parameter: cve_id. The full parameter table on this page comes from the server's own tool schema.
Register the DataNexus MCP server in PolicyLayer and add a rule for security_fetch_cve_detail: 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 DataNexus MCP. Nothing to install.
security_fetch_cve_detail 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 security_fetch_cve_detail 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 security_fetch_cve_detail. 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.
security_fetch_cve_detail is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DataNexus, and thousands of servers like it.
This server
Across the catalogue