Remove a membership from its project.
AI agents call remove_membership 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 project membership is a destructive action because it permanently revokes a user's access and role within a project. While technically re-addable, this is a distinct operation and the primary effect of this tool is to delete/revoke an access grant.
From the tool's definition Tool name is 'remove_membership' and description states 'Remove a membership from its project.' The verb 'remove' combined with membership termination represents an irreversible action that cannot be easily undone without re-adding the user.
Attacks that exploit this kind of access
Remove a membership from its project. 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_membership: 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_membership 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_membership 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_membership. 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_membership is provided by the Redmine MCP server (KalvadTech/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 →