cve_lookup
Full detail for a single CVE by ID (format CVE-YYYY-NNNN). Returns CVSS scores, weakness IDs, references, and affected products from the NVD.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cve-lookup.md
What cve_lookup does on Livedatalink
AI agents call cve_lookup 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, e.g. CVE-2024-3094. |
Parameters from the server's own tool schema.
Why cve_lookup is rated Low
This tool queries publicly available vulnerability data from the National Vulnerability Database (NVD) and returns structured information about known CVEs. It performs a read-only retrieval operation with no side effects, data modification, code execution, or destructive capabilities.
From the tool's definition Tool retrieves 'full detail for a single CVE by ID' and 'returns CVSS scores, weakness IDs, references, and affected products from the NVD.' No modification, deletion, or execution capabilities described.
Attacks that exploit this kind of access
The rule that runs cve_lookup 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_lookup, this is the rule to start with:
cve_lookup 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_lookup call is checked against it from then on.
Questions about cve_lookup
Full detail for a single CVE by ID (format CVE-YYYY-NNNN). Returns CVSS scores, weakness IDs, references, and affected products from the NVD. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cve_lookup 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 cve_lookup: 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_lookup 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_lookup 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_lookup. 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_lookup 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