user_invitation_search

user_invitation \u00b7 POST /userInvitation/search \u2014 Returns events Required: q, from, size.

Server Vicarius vRx MCP Server space-c0wboy/vicarius-vrx-mcp-server
Category Read
Risk class Low
Parameters 00 required

What user_invitation_search does on Vicarius vRx MCP Server

AI agents call user_invitation_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.

Why user_invitation_search needs a policy

This tool retrieves user invitation events without modifying data. It follows the Read category pattern: a search endpoint that queries and returns results. The server description also notes 'read-only safety enforcement,' further confirming this tool does not write, execute, or destroy data. Severity is low because querying invitation records poses minimal risk even if misused by an agent.

From the tool's definition Tool name is 'user_invitation_search' and description indicates 'Returns events' with parameters 'q, from, size' typical of query operations. The 'search' verb and return-only behavior (no create/update/delete language) indicate read-only retrieval.

Questions about user_invitation_search

What does the user_invitation_search tool do? +

user_invitation \u00b7 POST /userInvitation/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.

How do I enforce a policy on user_invitation_search? +

Register the Vicarius vRx MCP Server MCP server in PolicyLayer and add a rule for user_invitation_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.

What risk level is user_invitation_search? +

user_invitation_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit user_invitation_search? +

Yes. Add a rate_limit block to the user_invitation_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.

How do I block user_invitation_search completely? +

Set action: deny in the PolicyLayer policy for user_invitation_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.

What MCP server provides user_invitation_search? +

user_invitation_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.