Look up a single CVE Record v5.2 from the MITRE CVE List by ID (e.g. CVE-2024-3094). Lazy-fetched and cached 7 days. License: MITRE CVE Terms of Use, commercial redistribution permitted; the response includes the standard attribution block.
AI agents call get_cve_record to retrieve information from TensorFeed without modifying anything — 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 in CVE-YYYY-NNNNN form, case-insensitive |
Parameters from the server's own tool schema.
This is a straightforward data retrieval tool that queries the MITRE CVE database. It does not create, modify, delete, or execute anything—it only fetches and returns publicly available vulnerability information. The caching behavior confirms it is a read-only operation. No security or operational risk arises from an AI agent querying CVE records.
From the tool's definition Tool name is 'get_cve_record' and description states it 'Look[s] up a single CVE Record v5.2 from the MITRE CVE List by ID'.
Attacks that exploit this kind of access
Look up a single CVE Record v5.2 from the MITRE CVE List by ID (e.g. CVE-2024-3094). Lazy-fetched and cached 7 days. License: MITRE CVE Terms of Use, commercial redistribution permitted; the response includes the standard attribution block. It is categorised as a Read tool in the TensorFeed MCP Server, which means it retrieves data without modifying state.
get_cve_record 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 TensorFeed MCP server in PolicyLayer and add a rule for get_cve_record: 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 TensorFeed. Nothing to install.
get_cve_record 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 get_cve_record 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 get_cve_record. 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.
get_cve_record is provided by the TensorFeed MCP server (https://mcp.tensorfeed.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →