Get summary statistics about vulnerabilities. Shows counts by severity, status, vendor, and year, plus CVSS score metrics (average, min, max). Optionally scope stats to a specific vendor.
AI agents call get_vulnerability_stats to retrieve information from Vulnerability Registry MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates existing vulnerability data for analysis purposes. It performs read-only queries over a database, returning computed statistics without creating, modifying, deleting, or executing any operations. The optional vendor scoping parameter does not change its fundamental read-only nature. There is no evidence of destructive, financial, or code execution capabilities.
From the tool's definition Tool description states it 'Shows counts by severity, status, vendor, and year, plus CVSS score metrics' and is scoped to query and retrieve summary statistics about vulnerabilities.
Attacks that exploit this kind of access
Get summary statistics about vulnerabilities. Shows counts by severity, status, vendor, and year, plus CVSS score metrics (average, min, max). Optionally scope stats to a specific vendor. It is categorised as a Read tool in the Vulnerability Registry MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vulnerability Registry MCP Server MCP server in PolicyLayer and add a rule for get_vulnerability_stats: 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 Vulnerability Registry MCP Server. Nothing to install.
get_vulnerability_stats 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_vulnerability_stats 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_vulnerability_stats. 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_vulnerability_stats is provided by the Vulnerability Registry MCP Server MCP server (orcohen5/vulnerability-registry). 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 →