security_fetch_cisa_kev
Check whether a CVE is in the CISA Known Exploited Vulnerabilities (KEV) catalog. Read-only. No side effects. Idempotent. cve_id: CVE identifier in format CVE-YYYY-NNNNN e.g. CVE-2021-44228. Required. Returns in_kev (bool), date_added, due_date, ransomware_use, and notes from the CISA KEV catalog...
This record as markdown: /tools/dev-7bd0-mcp-server/security-fetch-cisa-kev.md
What security_fetch_cisa_kev does on DataNexus MCP
AI agents call security_fetch_cisa_kev 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_cisa_kev is rated Low
This is a straightforward read operation that queries public security data from the CISA KEV catalog. It retrieves and returns information about known exploited vulnerabilities without creating, modifying, deleting, executing code, or committing financial obligations. The tool explicitly declares itself read-only and idempotent, confirming no side effects.
From the tool's definition Tool description explicitly states 'Read-only. No side effects. Idempotent.' It 'Check[s] whether a CVE is in the CISA Known Exploited Vulnerabilities (KEV) catalog' and 'Returns in_kev (bool), date_added, due_date, ransomware_use, and notes' — pure data…
Attacks that exploit this kind of access
The rule that runs security_fetch_cisa_kev 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_cisa_kev, this is the rule to start with:
security_fetch_cisa_kev 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_cisa_kev call is checked against it from then on.
Questions about security_fetch_cisa_kev
Check whether a CVE is in the CISA Known Exploited Vulnerabilities (KEV) catalog. Read-only. No side effects. Idempotent. cve_id: CVE identifier in format CVE-YYYY-NNNNN e.g. CVE-2021-44228. Required. Returns in_kev (bool), date_added, due_date, ransomware_use, and notes from the CISA KEV catalog. KEV status answers 'Is this being actively exploited?' — a critical triage question not available in NIST NVD. Verified source: CISA KEV catalog (updated daily, cached). Use security_fetch_cve_detail for full CVE severity. Use security_fetch_cve_epss for exploit probability. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_fetch_cisa_kev", 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_cisa_kev 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_cisa_kev: 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_cisa_kev 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_cisa_kev 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_cisa_kev. 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_cisa_kev 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