This record as markdown: /tools/creativelead-unclick/get-cve-detail.md
What get_cve_detail does on UnClick
AI agents call get_cve_detail 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 |
|---|---|---|---|
cve_id | string | — | e.g. CVE-2023-12345 |
Parameters from the server's own tool schema.
Why get_cve_detail is rated Low
This tool retrieves CVE (Common Vulnerabilities and Exposures) information from a reference database. It performs a read-only lookup operation—no data is created, modified, deleted, or executed. The worst-case misuse would be an AI agent gathering vulnerability information, which poses minimal direct risk compared to tools that execute code or modify data.
From the tool's definition Tool name 'get_cve_detail' and description 'Get details for a specific CVE by ID' indicate a retrieval operation that queries vulnerability data without modification, execution, or destructive capability.
Attacks that exploit this kind of access
The rule that runs get_cve_detail 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_cve_detail, this is the rule to start with:
get_cve_detail 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_cve_detail call is checked against it from then on.
Questions about get_cve_detail
Get details for a specific CVE by ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
get_cve_detail accepts 1 parameter: cve_id. 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_cve_detail: 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_cve_detail 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_cve_detail 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_cve_detail. 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_cve_detail 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