kev_status_check
Check whether a CVE is in the CISA Known Exploited Vulnerabilities catalog. Returns date added, due date, ransomware association, and required action.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/kev-status-check.md
What kev_status_check does on Livedatalink
AI agents call kev_status_check to retrieve information from Livedatalink 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. |
Parameters from the server's own tool schema.
Why kev_status_check is rated Low
This tool performs a read-only query against the CISA KEV catalog to retrieve vulnerability status information. It has no side effects—it only retrieves and returns existing data. No code execution, data modification, or destructive operations are involved. The severity is low because misuse would only result in information disclosure of already-public vulnerability data.
From the tool's definition Tool name 'kev_status_check' and description 'Check whether a CVE is in the CISA Known Exploited Vulnerabilities catalog.
Attacks that exploit this kind of access
The rule that runs kev_status_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kev_status_check, this is the rule to start with:
kev_status_check 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 Livedatalink, apply this rule, and every kev_status_check call is checked against it from then on.
Questions about kev_status_check
Check whether a CVE is in the CISA Known Exploited Vulnerabilities catalog. Returns date added, due date, ransomware association, and required action. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
kev_status_check 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 Livedatalink MCP server in PolicyLayer and add a rule for kev_status_check: 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 Livedatalink. Nothing to install.
kev_status_check 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 kev_status_check 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 kev_status_check. 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.
kev_status_check is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue