AI agents call get_recent_cves to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
resultsPerPage | number | — |
Parameters from the server's own tool schema.
This is a read-only operation that fetches publicly available vulnerability information. There are no state changes, deletions, executions, or financial implications. The blast radius of misuse is minimal — an agent could only retrieve CVE data that is already public.
From the tool's definition Tool name is 'get_recent_cves' and description states 'Get recently published CVEs from NVD' — this retrieves/queries CVE data from the National Vulnerability Database with no side effects or modifications.
Attacks that exploit this kind of access
Get recently published CVEs from NVD. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
get_recent_cves accepts 1 parameter: resultsPerPage. 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 get_recent_cves: 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.
get_recent_cves 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 get_recent_cves 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 get_recent_cves. 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.
get_recent_cves 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.
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 →