Remove a user from a group. Note: This only succeeds if the user has a zero balance in the group.
AI agents call splitwise_remove_user_from_group to permanently remove resources in Splitwise MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a user from a group is a destructive action — it revokes their membership and access to the group's shared expenses and history. While the constraint (zero balance required) limits some risk, the removal itself is not easily reversible without re-inviting and re-adding the user, making it effectively irreversible in terms of the user's participation and any associated state.
From the tool's definition Remove a user from a group
Attacks that exploit this kind of access
Remove a user from a group. Note: This only succeeds if the user has a zero balance in the group. It is categorised as a Destructive tool in the Splitwise MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Splitwise MCP Server MCP server in PolicyLayer and add a rule for splitwise_remove_user_from_group: 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 Splitwise MCP Server. Nothing to install.
splitwise_remove_user_from_group is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the splitwise_remove_user_from_group 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 splitwise_remove_user_from_group. 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.
splitwise_remove_user_from_group is provided by the Splitwise MCP Server MCP server (svarun115/splitwise-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 →