This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/search-cve.md
What search_cve does on UnClick
AI agents call search_cve to retrieve information from UnClick 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 |
|---|---|---|---|
keyword | string | Yes | |
startIndex | number | — | |
cvssV3Severity | string | — | LOW, MEDIUM, HIGH, CRITICAL |
resultsPerPage | number | — |
Parameters from the server's own tool schema.
Why search_cve is rated Low
This tool retrieves information from the National Vulnerability Database (NVD) CVE records. Searching a database is a read-only operation with no ability to modify, delete, or execute code. The blast radius of misuse is minimal—an agent could only retrieve publicly available vulnerability information, which carries no financial, destructive, or execution risk.
From the tool's definition Tool name 'search_cve' and description 'Search the NVD CVE database' indicate a query operation against a public vulnerability database with no side effects.
Attacks that exploit this kind of access
The rule that runs search_cve safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_cve, this is the rule to start with:
search_cve is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every search_cve call is checked against it from then on.
Questions about search_cve
Search the NVD CVE database. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
search_cve accepts 4 parameters: keyword, startIndex, cvssV3Severity, resultsPerPage. Required: keyword. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for search_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 UnClick. Nothing to install.
search_cve 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_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.
Set action: deny in the PolicyLayer policy for search_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.
search_cve is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue