cisa_kev
CISA Known Exploited Vulnerabilities check: is a CVE (or up to 100) in CISA's KEV catalog, with date added, federal remediation due date, past-due flag, known ransomware use, required action and CWEs. Or search the catalog by vendor/product, recently added (?days=) or ransomware use. Complements ...
This record as markdown: /tools/com-it-scorptech-x402/cisa-kev.md
What cisa_kev does on ScorpTech x402 API
AI agents call cisa_kev to retrieve information from ScorpTech x402 API 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 | string | — | CVE id(s), comma-separated (max 100) |
days | integer | — | Search: added in the last N days (1-3650) |
limit | integer | — | Search: max results (1-500, default 50) |
vendor | string | — | Search: vendor/project substring (e.g. Microsoft) |
product | string | — | Search: product substring |
ransomware | boolean | — | Search: only entries with known ransomware campaign use |
Parameters from the server's own tool schema.
Why cisa_kev is rated Low
Even though cisa_kev only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs cisa_kev safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cisa_kev, this is the rule to start with:
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 ScorpTech x402 API, apply this rule, and every cisa_kev call is checked against it from then on.
Questions about cisa_kev
CISA Known Exploited Vulnerabilities check: is a CVE (or up to 100) in CISA's KEV catalog, with date added, federal remediation due date, past-due flag, known ransomware use, required action and CWEs. Or search the catalog by vendor/product, recently added (?days=) or ransomware use. Complements /v1/cve-lookup (NVD). Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/cisa-kev. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
cisa_kev accepts 6 parameters: cve, days, limit, vendor, product, ransomware. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for 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 ScorpTech x402 API. Nothing to install.
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 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 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.
cisa_kev is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue