vulnerability \u00b7 GET /vulnerability/count \u2014 Count objects by stuff. Required: q, searchQuerys.
AI agents call vulnerability_count to retrieve information from Vicarius vRx MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read operation that counts vulnerability records matching search criteria. It performs no mutations, deletions, or external executions. The GET HTTP method and counting functionality confirm it is a safe information retrieval tool with minimal risk if misused by an agent.
From the tool's definition Tool name 'vulnerability_count' and description indicate a GET endpoint that 'Count objects by stuff' with parameters 'q, searchQuerys'. GET requests are read-only operations that retrieve or query data without side effects.
Attacks that exploit this kind of access
vulnerability \u00b7 GET /vulnerability/count \u2014 Count objects by stuff. Required: q, searchQuerys. It is categorised as a Read tool in the Vicarius vRx MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vicarius vRx MCP Server MCP server in PolicyLayer and add a rule for vulnerability_count: 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 Vicarius vRx MCP Server. Nothing to install.
vulnerability_count 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 vulnerability_count 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 vulnerability_count. 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.
vulnerability_count is provided by the Vicarius vRx MCP Server MCP server (space-c0wboy/vicarius-vrx-mcp-server). 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 →