Low Risk

list_kev_entries

list_kev_entries

How to control list_kev_entries ↓

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

Low Risk

Even though list_kev_entries only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_kev_entries": {}
  }
}

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

  1. Create a free account and register VulnMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_kev_entries tool do? +

list_kev_entries. It is categorised as a Read tool in the VulnMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_kev_entries? +

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

What risk level is list_kev_entries? +

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

Can I rate-limit list_kev_entries? +

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

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

list_kev_entries is provided by the Vuln MCP server (vulnerability-lookup/vulnmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every VulnMCP tool call.

Deterministic rules across all 16 VulnMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

16 VulnMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.