Low Risk

search_vulnerabilities

Search the Exploit Intelligence Platform for vulnerabilities (CVEs). Returns a list of matching CVEs with CVSS scores, EPSS exploitation probability, exploit counts, CISA KEV status, VulnCheck KEV, InTheWild.io exploitation signals, and ransomware attribution. Supports full-text search, severity/...

Risk signalsAccepts freeform code/query input (query) · High parameter count (21 properties)

Part of the Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database server.

search_vulnerabilities is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE EXPLOIT INTELLIGENCE PLATFORM — CVE, VULNERABILITY AND EXPLOIT DATABASE →

Free to start. No card required.

AI agents call search_vulnerabilities to retrieve information from Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though search_vulnerabilities only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database policy for all 17 tools.

Get this rule live on your own Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY EXPLOIT INTELLIGENCE PLATFORM — CVE, VULNERABILITY AND EXPLOIT DATABASE →

View all 17 tools →

These attack patterns abuse exactly the kind of access search_vulnerabilities gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so search_vulnerabilities only ever does what you allow.

SECURE EXPLOIT INTELLIGENCE PLATFORM — CVE, VULNERABILITY AND EXPLOIT DATABASE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the search_vulnerabilities tool do? +

Search the Exploit Intelligence Platform for vulnerabilities (CVEs). Returns a list of matching CVEs with CVSS scores, EPSS exploitation probability, exploit counts, CISA KEV status, VulnCheck KEV, InTheWild.io exploitation signals, and ransomware attribution. Supports full-text search, severity/vendor/product/ecosystem/CWE filters, CVSS/EPSS thresholds, plus any_exploited and ransomware filters. When sort is omitted, the API may automatically prefer newest exploitation, exploit, or nuclei-template activity based on the filters you set. Examples: query='apache httpd' with has_exploits=true; vendor='fortinet' with severity='critical' and is_kev=true sorted by epss_desc; any_exploited=true with ransomware=true for ransomware-linked CVEs; cwe='89' with min_cvss=9 for critical SQL injection CVEs.. It is categorised as a Read tool in the Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_vulnerabilities? +

Register the Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database MCP server in PolicyLayer and add a rule for search_vulnerabilities: 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 Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database. Nothing to install.

What risk level is search_vulnerabilities? +

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

Can I rate-limit search_vulnerabilities? +

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

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

search_vulnerabilities is provided by the Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database MCP server (pypi:eip-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database tool call.

Deterministic rules across all 17 Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.