Remove a user from a group. ADMIN ONLY.
AI agents use remove_user_from_group to create or update resources in Open WebUI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Open WebUI MCP Server environment.
Removing a user from a group modifies access/membership data but is reversible (the user can be re-added). This falls under Write rather than Destructive since no data is permanently deleted. The ADMIN ONLY restriction indicates elevated privilege, raising severity to medium.
From the tool's definition 'Remove a user from a group. ADMIN ONLY.' — removes a user from a group, which is a reversible modification to group membership.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access remove_user_from_group gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Open WebUI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_user_from_group:
{
"version": "1",
"default": "deny",
"tools": {
"remove_user_from_group": {
"limits": [
{
"counter": "remove_user_from_group_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} remove_user_from_group 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.
Free to start. No card required.
Remove a user from a group. ADMIN ONLY. It is categorised as a Write tool in the Open WebUI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Open WebUI MCP Server MCP server in PolicyLayer and add a rule for 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 Open WebUI MCP Server. Nothing to install.
remove_user_from_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the 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 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.
remove_user_from_group is provided by the Open WebUI MCP Server MCP server (troylar/open-webui-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Open WebUI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
82 Open WebUI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.