cve_search_by_vendor
Search CVEs by vendor with optional product and date range filters. Vendor is matched against the NVD CPE namespace, e.g. 'apache', 'microsoft'.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/cve-search-by-vendor.md
What cve_search_by_vendor does on Livedatalink
AI agents call cve_search_by_vendor 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 |
|---|---|---|---|
limit | number | — | Max results to return (1-2000, default 20). |
vendor | string | Yes | Vendor name, lowercase preferred. |
product | string | — | Optional product name filter. |
pub_end_date | string | — | ISO date or YYYY-MM-DD upper bound on published date. |
pub_start_date | string | — | ISO date or YYYY-MM-DD lower bound on published date. |
Parameters from the server's own tool schema.
Why cve_search_by_vendor is rated Low
This tool retrieves and queries vulnerability data from the NVD (National Vulnerability Database) based on vendor, product, and date filters. It performs searches only—no creation, modification, deletion, or execution of code/commands. The output is informational cybersecurity intelligence useful for vulnerability assessment, with no side effects on external systems or data stores.
From the tool's definition Tool name 'cve_search_by_vendor' and description 'Search CVEs by vendor' with filtering capabilities; the verb 'search' and the read-only nature of querying a CVE database indicate pure information retrieval with no data modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs cve_search_by_vendor 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_search_by_vendor, this is the rule to start with:
cve_search_by_vendor 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_search_by_vendor call is checked against it from then on.
Questions about cve_search_by_vendor
Search CVEs by vendor with optional product and date range filters. Vendor is matched against the NVD CPE namespace, e.g. 'apache', 'microsoft'. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
cve_search_by_vendor accepts 5 parameters: limit, vendor, product, pub_end_date, pub_start_date. Required: vendor. 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_search_by_vendor: 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_search_by_vendor 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_search_by_vendor 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_search_by_vendor. 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_search_by_vendor 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