Busca vulnerabilidades CVE relacionadas con un producto, vendor o keyword.
AI agents call search_cves_by_keyword to retrieve information from MCP Cybersecurity Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves CVE vulnerability information based on keywords, vendors, or products. It has no capability to modify, delete, or execute operations—it only returns data from a vulnerability database. This is a standard read operation with minimal security risk, appropriate for Blue Team and SOC operations that need to research known vulnerabilities.
From the tool's definition Tool description indicates it 'searches vulnerabilities' (busca vulnerabilidades) and retrieves CVE data through queries.
Attacks that exploit this kind of access
Busca vulnerabilidades CVE relacionadas con un producto, vendor o keyword. It is categorised as a Read tool in the MCP Cybersecurity Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Cybersecurity Server MCP server in PolicyLayer and add a rule for search_cves_by_keyword: 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 Cybersecurity Server. Nothing to install.
search_cves_by_keyword is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_cves_by_keyword 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.
Set action: deny in the PolicyLayer policy for search_cves_by_keyword. 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.
search_cves_by_keyword is provided by the MCP Cybersecurity Server MCP server (josemiteba/mcp-cybersecurity-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →