nvd.cves.detail

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nvd.cves.detail.md

WHAT IT DOES

What nvd.cves.detail does on Apibase

AI agents call nvd.cves.detail to retrieve information from Apibase 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	Yes	Full CVE identifier in canonical form (e.g. 'CVE-2021-44228' for Log4Shell). Format: CVE-YYYY-NNNN+ where YYYY is the year and NNNN+ is a sequence number of fou

Parameters from the server's own tool schema.

RISK

Why nvd.cves.detail is rated Low

Tool retrieves vulnerability data without modifying systems, executing code, or committing financial obligations.

From the tool's definition Fetch the canonical NVD record for a specific CVE-ID

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nvd.cves.detail safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nvd.cves.detail, this is the rule to start with:

nvd.cves.detail Allowed

nvd.cves.detail is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nvd.cves.detail": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every nvd.cves.detail call is checked against it from then on.

FAQ

Questions about nvd.cves.detail

What does the nvd.cves.detail tool do? +

Fetch the canonical NVD record for a specific CVE-ID — full English description, CVSS v3 + v2 vectors and scores, weakness types (CWE), affected CPE configurations with version ranges, and all references with tags. Example: CVE-2021-44228 for Log4Shell. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does nvd.cves.detail accept? +

nvd.cves.detail accepts 1 parameter: cve_id. Required: cve_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on nvd.cves.detail? +

Register the Apibase MCP server in PolicyLayer and add a rule for nvd.cves.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 Apibase. Nothing to install.

What risk level is nvd.cves.detail? +

nvd.cves.detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nvd.cves.detail? +

Yes. Add a rate_limit block to the nvd.cves.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.

How do I block nvd.cves.detail completely? +

Set action: deny in the PolicyLayer policy for nvd.cves.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.

What MCP server provides nvd.cves.detail? +

nvd.cves.detail is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →