cve-mitre.cves.id_status
Check a CVE ID's current lifecycle state (RESERVED, PUBLISHED, or REJECTED) and which CNA owns/assigned it, even for IDs that have been reserved but have no published record yet. NVD has no equivalent — it only indexes published records. Data: cveawg.mitre.org (CVE Program, MITRE Corporation), no...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cve-mitre.cves.id-status.md
What cve-mitre.cves.id_status does on Apibase
AI agents call cve-mitre.cves.id_status 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 to check, e.g. "CVE-2021-44228". Returns state (RESERVED/PUBLISHED/REJECTED) and the assigning CNA even for IDs with no published record yet. |
Parameters from the server's own tool schema.
Why cve-mitre.cves.id_status is rated Low
Tool retrieves CVE metadata status information with no side effects or data modification capabilities.
From the tool's definition Check a CVE ID's current lifecycle state and which CNA owns it.
Attacks that exploit this kind of access
The rule that runs cve-mitre.cves.id_status 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.id_status, this is the rule to start with:
cve-mitre.cves.id_status 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.id_status call is checked against it from then on.
Questions about cve-mitre.cves.id_status
Check a CVE ID's current lifecycle state (RESERVED, PUBLISHED, or REJECTED) and which CNA owns/assigned it, even for IDs that have been reserved but have no published record yet. NVD has no equivalent — it only indexes published records. 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.id_status 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.id_status: 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.id_status 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.id_status 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.id_status. 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.id_status 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