get_cve_timeline

Build a complete CVE lifecycle timeline: NVD publication date, EPSS score history, CISA KEV addition date, patch lag, and exploit window estimation. Args: cve_id: CVE identifier (e.g. CVE-2021-44228)

ServerCVE MCP Server
CategoryRead

How to control get_cve_timeline ↓

WHAT IT DOES

What get_cve_timeline does on CVE MCP Server

AI agents call get_cve_timeline to retrieve information from CVE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why get_cve_timeline needs a policy

This is a pure data retrieval and aggregation tool that queries multiple security intelligence sources to construct a timeline view of CVE lifecycle events. It has no side effects, does not execute code or commands, does not modify any data, and does not trigger destructive or financial operations. The word 'Build' refers to composing a report from existing data, not creating or modifying records.

From the tool's definition Tool retrieves and aggregates historical timeline data (NVD publication date, EPSS score history, CISA KEV addition date, patch lag, exploit window estimation) about CVEs without modifying any data or triggering external actions.

Documented attack patterns abuse exactly the kind of access get_cve_timeline gives an agent:

POLICY

How to control get_cve_timeline

PolicyLayer is an MCP gateway — it sits between your AI agents and CVE MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_cve_timeline:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_cve_timeline": {}
  }
}

get_cve_timeline is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register CVE MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More CVE MCP Server tools

Read parse_cvss Parse and explain a CVSS vector string (v2, v3.x, or v4.0). Args: vector: CVS Read calculate_risk_score Calculate a composite 0-100 risk score using CVSS, EPSS, KEV, and PoC data. Read check_exploit_availability Search GitHub for public proof-of-concept (PoC) exploit repositories for a CVE. Result Read check_ip_reputation Check an IP address reputation via AbuseIPDB and GreyNoise Community. Returns abuse co Read check_kev Check if a CVE is in the CISA Known Exploited Vulnerabilities (KEV) catalog. Args: Read check_package_vulns Check a package for known vulnerabilities via OSV.dev. Args: package: Package Read check_poc_exists Search for proof-of-concept exploits across GitHub, Exploit-DB, and Nuclei templates. Read check_ransomware_intel Check if a Bitcoin address is associated with a known ransomware family using the Rans

All 27 CVE MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_cve_timeline

What does the get_cve_timeline tool do? +

Build a complete CVE lifecycle timeline: NVD publication date, EPSS score history, CISA KEV addition date, patch lag, and exploit window estimation. Args: cve_id: CVE identifier (e.g. CVE-2021-44228). It is categorised as a Read tool in the CVE MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cve_timeline? +

Register the CVE MCP Server MCP server in PolicyLayer and add a rule for get_cve_timeline: 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 CVE MCP Server. Nothing to install.

What risk level is get_cve_timeline? +

get_cve_timeline is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_cve_timeline? +

Yes. Add a rate_limit block to the get_cve_timeline 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.

How do I block get_cve_timeline completely? +

Set action: deny in the PolicyLayer policy for get_cve_timeline. 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.

What MCP server provides get_cve_timeline? +

get_cve_timeline is provided by the CVE MCP Server MCP server (mukul975/cve-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CVE MCP Server tool call.

Start from CVE MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

27 CVE MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.