cisa-kev-get

Look up a single CVE in the CISA KEV catalog. Returns the catalog

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/cisa-kev-get.md

WHAT IT DOES

What cisa-kev-get does on Meta Data Mcp

AI agents call cisa-kev-get 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 cisa-kev-get is rated Low

This tool performs a read-only lookup of publicly available CVE vulnerability data from the CISA Known Exploited Vulnerabilities catalog. It queries and returns information with no side effects, modifications, or irreversible actions. The severity is low because accessing public vulnerability metadata poses minimal risk—the data is intended for public consumption to improve security awareness.

From the tool's definition Tool name 'cisa-kev-get' and description 'Look up a single CVE in the CISA KEV catalog. Returns the catalog' indicate a query operation that retrieves vulnerability information without modifying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cisa-kev-get 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 cisa-kev-get, this is the rule to start with:

cisa-kev-get Allowed

cisa-kev-get 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": {
    "cisa-kev-get": {}
  }
}

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 cisa-kev-get call is checked against it from then on.

FAQ

Questions about cisa-kev-get

What does the cisa-kev-get tool do? +

Look up a single CVE in the CISA KEV catalog. Returns the catalog. 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 cisa-kev-get? +

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

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

Can I rate-limit cisa-kev-get? +

Yes. Add a rate_limit block to the cisa-kev-get 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 cisa-kev-get completely? +

Set action: deny in the PolicyLayer policy for cisa-kev-get. 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 cisa-kev-get? +

cisa-kev-get 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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