This record as markdown: /tools/creativelead-unclick/get-recent-cves.md
What get_recent_cves does on UnClick
AI agents call get_recent_cves 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 |
|---|---|---|---|
resultsPerPage | number | — |
Parameters from the server's own tool schema.
Why get_recent_cves is rated Low
This tool queries and retrieves CVE (Common Vulnerabilities and Exposures) data from the National Vulnerability Database. It performs data retrieval without modifying, deleting, or executing any code. The information retrieved is already public. Even though CVE data relates to security vulnerabilities, the tool itself only reads and does not exploit or trigger any vulnerabilities.
From the tool's definition Tool description states 'Get recently published CVEs from NVD' — a pure retrieval operation with no side effects. CVE data is public information and the operation is read-only.
Attacks that exploit this kind of access
The rule that runs get_recent_cves 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 get_recent_cves, this is the rule to start with:
get_recent_cves 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 get_recent_cves call is checked against it from then on.
Questions about get_recent_cves
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 (creativelead/unclick). 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