Remove participants from a group
AI agents call remove_participants to permanently remove resources in Evolution API WhatsApp MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing participants from a group is a destructive operation: once removed, the participant loses access to the group's history and membership, and the action cannot be undone automatically. The blast radius is high because an AI agent could remove many participants across multiple groups, causing significant disruption to business communications.
From the tool's definition 'Remove participants from a group' — removing participants is an irreversible action that expels users from a group without their consent
Attacks that exploit this kind of access
Remove participants from a group. It is categorised as a Destructive tool in the Evolution API WhatsApp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Evolution API WhatsApp MCP Server MCP server in PolicyLayer and add a rule for remove_participants: 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 Evolution API WhatsApp MCP Server. Nothing to install.
remove_participants 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_participants 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_participants. 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_participants is provided by the Evolution API WhatsApp MCP Server MCP server (luiso2/mcp-evolution-api). 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 →