user \u00b7 POST /user/search \u2014 Returns events Required: q, from, size.
AI agents call user_search 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 search operation that retrieves user events data based on query parameters. The verb 'search' and the description 'Returns events' indicate data retrieval without modification, creation, deletion, or execution of external operations. Despite the POST HTTP method (which may be used for search payloads), the functional behavior is read-only.
From the tool's definition Tool name is 'user_search' and description indicates 'Returns events' with required query parameters (q, from, size), consistent with a search/query operation with no modification or side effects.
Attacks that exploit this kind of access
user \u00b7 POST /user/search \u2014 Returns events Required: q, from, size. 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 user_search: 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.
user_search 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 user_search 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 user_search. 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.
user_search 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 →