cve_status
AI agents call cve_status 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.
Given the context that this is a CVE risk assessment server focused on lookups, ranking, and patch prioritization, cve_status most likely retrieves vulnerability status information without modifying data or executing external operations. The absence of descriptive text lowers confidence, but the tool naming pattern and server purpose strongly suggest a read-only informational operation with minimal blast radius.
From the tool's definition Tool name 'cve_status' with no description provided; inferred from sibling tools on this server (cve_lookup, cve_rank, cve_refresh, cve_patch_first, cve_export, cve_config) which are all read or informational operations.
Attacks that exploit this kind of access
cve_status. 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_status: 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_status 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_status 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_status. 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_status 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 →