user_invitation_update · Vicarius vRx MCP Server MCP

WHAT IT DOES

What user_invitation_update does on Vicarius vRx MCP Server

AI agents use user_invitation_update to create or update resources in Vicarius vRx MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vicarius vRx MCP Server environment.

WHY IT NEEDS A POLICY

Why user_invitation_update needs a policy

This tool modifies user invitation records via an update operation, which is a reversible write action. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or involve financial transactions. The medium severity reflects that misconfigured user invitations could enable unauthorized access or escalate privileges, but the scope is limited to invitation management.

From the tool's definition Tool name 'user_invitation_update' and HTTP method 'POST /userInvitation/update' indicate modification of invitation records. The description states 'Update instance of the object', confirming this performs a reversible write operation on user invitation data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

user_invitation_update Rate-limited

user_invitation_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "user_invitation_update": {
      "limits": [
        {
          "counter": "user_invitation_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Vicarius vRx MCP Server, so you can run agents against it safely.

FAQ

Questions about user_invitation_update

What does the user_invitation_update tool do? +

user_invitation \u00b7 POST /userInvitation/update \u2014 Update instance of the object Requires a JSON request body. It is categorised as a Write tool in the Vicarius vRx MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on user_invitation_update? +

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

user_invitation_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit user_invitation_update? +

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

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

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