cve_security_lookup

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io

Low RISK CLASS

Category Read

Parameters 61 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/cve-security-lookup.md

WHAT IT DOES

What cve_security_lookup does on Mcp Knowledge

AI agents call cve_security_lookup to retrieve information from Mcp Knowledge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`mode`	string	—	Override auto-detection: "lookup" for exact CVE ID, "search" for product/vendor keyword.
`async`	boolean	—	If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
`query`	string	Yes	CVE ID (e.g. "CVE-2024-3094") or product/vendor keyword (e.g. "openssl", "Apache Tomcat"). Mode is auto-detected from the CVE-YYYY-XXXXX pattern.
`max_results`	number	—	Maximum number of vulnerabilities to return (default 20, max 50).
`severity_min`	string	—	Minimum CVSS v3 severity to include in results (default: no filter).
`published_after`	string	—	ISO date YYYY-MM-DD — only include CVEs published after this date. Defaults to 365 days ago for search mode.

Parameters from the server's own tool schema.

RISK

Why cve_security_lookup is rated Low

This is a read-only information retrieval tool that queries authoritative security databases (NVD NIST, CISA KEV, EPSS FIRST, GitHub Security Advisories) to surface vulnerability metadata. It enables passive analysis and research with zero side effects on systems or data.

From the tool's definition Tool performs 'Look up', 'search', and 'cross-references' vulnerability data from external databases. Returns 'structured vulnerability records' with no indication of modification, creation, deletion, or execution capabilities.

Risk signalsAccepts freeform code/query input (query)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cve_security_lookup safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cve_security_lookup, this is the rule to start with:

cve_security_lookup Allowed

cve_security_lookup 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": {
    "cve_security_lookup": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every cve_security_lookup call is checked against it from then on.

FAQ

Questions about cve_security_lookup

What does the cve_security_lookup tool do? +

Look up CVE vulnerability data for enterprise security teams, DevSecOps and SOC analysts. Supports two modes: exact CVE ID lookup (e.g. 'CVE-2024-3094') or keyword search by product/vendor (e.g. 'openssl', 'Apache Tomcat'). Cross-references four authoritative keyless sources: NVD NIST (official CVE database, CVSS v3 scores, affected CPEs), CISA KEV (Known Exploited Vulnerabilities catalog — exploit_in_wild flag), EPSS FIRST (exploit probability 0-1), GitHub Security Advisories (ecosystem-specific: npm/pypi/maven). Returns structured vulnerability records with CVSS v3 scores, affected product version ranges, CWE weakness classification, references and exploitation status. Signals engine produces P0/P1/P2 alerts: P0=CVSS>=9 + active exploitation, P1=CVSS>=7 or EPSS>=70%, P2=CWE pattern clusters. Relevant for EU NIS2 and DORA supply chain risk obligations. Optional env: NVD_API_KEY (raises NVD rate-limit 5→50 req/30s), GITHUB_TOKEN (raises GHSA GraphQL rate-limit). Cache TTL 6h. SLA <=25s p95. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.

What parameters does cve_security_lookup accept? +

cve_security_lookup accepts 6 parameters: mode, async, query, max_results, severity_min, published_after. Required: query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on cve_security_lookup? +

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

What risk level is cve_security_lookup? +

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

Can I rate-limit cve_security_lookup? +

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

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

cve_security_lookup is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Knowledge, and thousands of servers like it.

This server

All 271 Mcp Knowledge tools →

Across the catalogue

The MCP Attack Database →

Guides

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