cve_rank
AI agents call cve_rank to retrieve information from CVE Risk MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to rank or sort existing CVE vulnerability data based on risk scores and exploitation status. This is a read operation that retrieves and presents information without modifying, deleting, or executing external operations. The empty description lowers confidence slightly, but context from the server's stated purpose and sibling tools strongly suggests a read-only ranking/sorting capability.
From the tool's definition Tool name 'cve_rank' and server description indicate ranking/sorting of CVE data. No description provided for the tool itself, but sibling tools (cve_lookup, cve_status, cve_patch_first) suggest read-only vulnerability assessment operations.
Attacks that exploit this kind of access
cve_rank. It is categorised as a Read tool in the CVE Risk MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CVE Risk MCP Server MCP server in PolicyLayer and add a rule for cve_rank: 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 CVE Risk MCP Server. Nothing to install.
cve_rank 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 cve_rank 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 cve_rank. 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.
cve_rank is provided by the CVE Risk MCP Server MCP server (sarveshkapre/cve-risk-mcp). 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 →