Remove a user from a group. Requires admin privileges.
AI agents call remove_user_from_group to permanently remove resources in Redmine — 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 revokes their group-based permissions and access rights. While technically a new 'add' operation could restore membership, the removal itself is a destructive, privilege-altering action with significant security implications (loss of access to projects, issues, etc.). The requirement for admin privileges underscores the high blast radius if misused by an AI agent.
From the tool's definition 'Remove a user from a group' — removal of group membership is irreversible in the sense that the access/permissions change takes effect immediately and the action cannot be passively undone without a new write operation.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Remove a user from a group. Requires admin privileges. It is categorised as a Destructive tool in the Redmine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Redmine 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 Redmine. Nothing to install.
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 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 Redmine MCP server (yenpu/redmine-mcp). 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 →