circl-cve-last

Fetch the most recent CVEs from CIRCL.

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/circl-cve-last.md

WHAT IT DOES

What circl-cve-last does on Meta Data Mcp

AI agents call circl-cve-last 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 circl-cve-last is rated Low

The tool queries and retrieves CVE (Common Vulnerabilities and Exposures) data from CIRCL without modifying, executing, or deleting anything. This is a straightforward data retrieval operation consistent with other sibling tools like arxiv-query and au-data-gov-get-dataset. While CVE information is security-sensitive, accessing it does not pose inherent misuse risk (the data is public).

From the tool's definition Tool description states 'Fetch the most recent CVEs' — a read-only operation that retrieves data from an open API with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs circl-cve-last 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 circl-cve-last, this is the rule to start with:

circl-cve-last Allowed

circl-cve-last 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": {
    "circl-cve-last": {}
  }
}

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 circl-cve-last call is checked against it from then on.

FAQ

Questions about circl-cve-last

What does the circl-cve-last tool do? +

Fetch the most recent CVEs from CIRCL. 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 circl-cve-last? +

Register the Meta Data MCP server in PolicyLayer and add a rule for circl-cve-last: 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 circl-cve-last? +

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

Can I rate-limit circl-cve-last? +

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

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

circl-cve-last 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 →