Low Risk

get_cve

Get details for a specific CVE ID. Source: cve-search.org

How to control get_cve ↓

What get_cve does on RAD Security

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

Low Risk

Why get_cve needs a policy

This tool performs a read-only lookup of CVE vulnerability data. It retrieves and returns security metadata about known vulnerabilities but does not create, modify, delete, or execute any operations. Even though CVE information relates to security, the tool itself is purely informational/query-based with no side effects.

From the tool's definition Tool name is 'get_cve' and description states 'Get details for a specific CVE ID' — this is a retrieval operation that queries an external CVE database (cve-search.org) and returns vulnerability information without modifying any data.

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

How to control get_cve

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

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

get_cve 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 RAD Security — 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.

Related tools and policies

Go deeper

Questions about get_cve

What does the get_cve tool do? +

Get details for a specific CVE ID. Source: cve-search.org. It is categorised as a Read tool in the RAD Security MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cve? +

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

What risk level is get_cve? +

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

Can I rate-limit get_cve? +

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

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

get_cve is provided by the RAD Security MCP server (rad-security/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 RAD Security tool call.

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

Free to start. No card required.

55 RAD Security tools catalogued and risk-classified — across an index of 43,000+ 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.