nvd-cve-history

List CVE change-history events. Filter by CVE id or change date range; paginate with startIndex.

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/nvd-cve-history.md

WHAT IT DOES

What nvd-cve-history does on Meta Data Mcp

AI agents call nvd-cve-history to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why nvd-cve-history is rated Low

This tool queries the National Vulnerability Database (NVD) to retrieve CVE (Common Vulnerabilities and Exposures) change history. It performs filtering and pagination on existing data but does not create, modify, delete, or execute any operations.

From the tool's definition Tool name 'nvd-cve-history' and description 'List CVE change-history events. Filter by CVE id or change date range; paginate with startIndex' indicate a query operation that retrieves historical vulnerability data without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nvd-cve-history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nvd-cve-history, this is the rule to start with:

nvd-cve-history Allowed

nvd-cve-history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nvd-cve-history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every nvd-cve-history call is checked against it from then on.

FAQ

Questions about nvd-cve-history

What does the nvd-cve-history tool do? +

List CVE change-history events. Filter by CVE id or change date range; paginate with startIndex. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on nvd-cve-history? +

Register the Meta Data MCP server in PolicyLayer and add a rule for nvd-cve-history: 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 Meta Data Mcp. Nothing to install.

What risk level is nvd-cve-history? +

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

Can I rate-limit nvd-cve-history? +

Yes. Add a rate_limit block to the nvd-cve-history 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 nvd-cve-history completely? +

Set action: deny in the PolicyLayer policy for nvd-cve-history. 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 nvd-cve-history? +

nvd-cve-history is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Data, and thousands of servers like it.

This server

All 396 Meta Data tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →