cve-mitre.cves.record
Fetch the full canonical CVE record as published by the assigning CNA (CVE Numbering Authority) in CVE JSON 5.x format — title, description, affected vendor/product/version ranges, CVSS score/vector (if scored), CWE weakness types, and references. This is the authoritative source record; distinct...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cve-mitre.cves.record.md
What cve-mitre.cves.record does on Apibase
AI agents call cve-mitre.cves.record 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 | CVE identifier, e.g. "CVE-2021-44228" (Log4Shell) or "CVE-2024-3400". |
Parameters from the server's own tool schema.
Why cve-mitre.cves.record is rated Low
Tool retrieves CVE security data with no side effects or modifications.
From the tool's definition Fetch the full canonical CVE record
Attacks that exploit this kind of access
The rule that runs cve-mitre.cves.record 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 cve-mitre.cves.record, this is the rule to start with:
cve-mitre.cves.record 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 Apibase, apply this rule, and every cve-mitre.cves.record call is checked against it from then on.
Questions about cve-mitre.cves.record
Fetch the full canonical CVE record as published by the assigning CNA (CVE Numbering Authority) in CVE JSON 5.x format — title, description, affected vendor/product/version ranges, CVSS score/vector (if scored), CWE weakness types, and references. This is the authoritative source record; distinct from nvd.cves.detail, which serves NIST's downstream-enriched copy (added CPE configurations, NVD-analyst CVSS). Example: CVE-2021-44228 (Log4Shell). Data: cveawg.mitre.org (CVE Program, MITRE Corporation), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
cve-mitre.cves.record accepts 1 parameter: cve_id. Required: cve_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for cve-mitre.cves.record: 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.
cve-mitre.cves.record 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 cve-mitre.cves.record 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 cve-mitre.cves.record. 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.
cve-mitre.cves.record 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.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue