cve_recent
Recent CVEs published in the last N days (default 7, max 120). Optional vendor and severity filters (CRITICAL, HIGH, MEDIUM, LOW).
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cve-recent.md
What cve_recent does on Livedatalink
AI agents call cve_recent 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 |
|---|---|---|---|
days | number | — | Lookback window in days (1-120). |
limit | number | — | Max results (default 50). |
vendor | string | — | Optional vendor filter. |
severity | string | — | Optional CVSS severity filter: CRITICAL, HIGH, MEDIUM, or LOW. |
Parameters from the server's own tool schema.
Why cve_recent is rated Low
This is a data retrieval tool that queries a CVE database and returns filtered results. It has no side effects, does not execute code or commands, does not modify data, and does not move money. The low severity reflects that misuse (e.g., an agent requesting CVEs for a specific vendor) would only return informational data useful for security research, with no ability to harm systems directly.
From the tool's definition Tool name 'cve_recent' and description explicitly states it retrieves/queries 'Recent CVEs published in the last N days' with optional filters.
Attacks that exploit this kind of access
The rule that runs cve_recent 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 cve_recent, this is the rule to start with:
cve_recent 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 cve_recent call is checked against it from then on.
Questions about cve_recent
Recent CVEs published in the last N days (default 7, max 120). Optional vendor and severity filters (CRITICAL, HIGH, MEDIUM, LOW). It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cve_recent accepts 4 parameters: days, limit, vendor, severity. 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 cve_recent: 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.
cve_recent 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_recent 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_recent. 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_recent 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