user_invitation_delete

user_invitation \u00b7 DELETE /userInvitation/delete \u2014 Disable instance of the object. Requires a JSON request body.

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

What user_invitation_delete does on Vicarius vRx MCP Server

AI agents call user_invitation_delete to permanently remove resources in Vicarius vRx MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why user_invitation_delete needs a policy

This tool irreversibly deletes or disables user invitation objects. Even though the description uses 'disable' rather than explicit deletion, DELETE operations on invitation records represent data removal that cannot be undone. This is more severe than Write (which is reversible modification) and qualifies as Destructive.

From the tool's definition Tool name 'user_invitation_delete' combined with description stating 'DELETE /userInvitation/delete — Disable instance of the object.' The HTTP method is DELETE and the operation permanently removes/disables user invitation records, which cannot be undone.

Questions about user_invitation_delete

What does the user_invitation_delete tool do? +

user_invitation \u00b7 DELETE /userInvitation/delete \u2014 Disable instance of the object. Requires a JSON request body. It is categorised as a Destructive tool in the Vicarius vRx MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on user_invitation_delete? +

Register the Vicarius vRx MCP Server MCP server in PolicyLayer and add a rule for user_invitation_delete: 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_delete? +

user_invitation_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit user_invitation_delete? +

Yes. Add a rate_limit block to the user_invitation_delete 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_delete completely? +

Set action: deny in the PolicyLayer policy for user_invitation_delete. 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_delete? +

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