waha_remove_group_participants

THE RISK

Critical Risk

Why waha_remove_group_participants needs a policy

Removing group participants is a destructive, non-reversible operation. Once removed, members lose access to the group and its history, and must be re-invited manually. The blast radius is high since an AI agent could mass-remove participants from groups, disrupting communications and communities.

From the tool's definition 'Remove member(s) from a group' — removing participants is an irreversible action that ejects users from the group, cannot be easily undone without re-inviting each member

Risk signalsAdmin/system-level operation

Documented attack patterns abuse exactly the kind of access waha_remove_group_participants gives an agent:

POLICY

How to control waha_remove_group_participants

PolicyLayer is an MCP gateway — it sits between your AI agents and WAHA MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for waha_remove_group_participants:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "waha_remove_group_participants"
  ]
}

waha_remove_group_participants disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register WAHA MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More WAHA MCP Server tools

Destructive waha_clear_chat_messages Clear all messages from a chat. WARNING: This is a destructive operation that cannot be un Destructive waha_delete_chat Delete a chat completely. WARNING: This is a destructive operation that cannot be undone. Destructive waha_delete_group_picture Remove group profile picture. Destructive waha_delete_message Delete a specific message from a chat. This is a destructive operation and cannot be undon Destructive waha_leave_group Leave a group. Execute waha_revoke_group_invite_code Revoke current invite link and generate a new one. Requires admin privileges. Write waha_demote_group_admin Remove admin privileges from participant(s). Requires admin privileges. Write waha_react_to_message Add an emoji reaction to a message. To remove a reaction, send an empty string.

All 52 WAHA MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in WAHA MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about waha_remove_group_participants

What does the waha_remove_group_participants tool do? +

Remove member(s) from a group. Requires admin privileges. It is categorised as a Destructive tool in the WAHA MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on waha_remove_group_participants? +

Register the WAHA MCP Server MCP server in PolicyLayer and add a rule for waha_remove_group_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 WAHA MCP Server. Nothing to install.

What risk level is waha_remove_group_participants? +

waha_remove_group_participants is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit waha_remove_group_participants? +

Yes. Add a rate_limit block to the waha_remove_group_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.

How do I block waha_remove_group_participants completely? +

Set action: deny in the PolicyLayer policy for waha_remove_group_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.

What MCP server provides waha_remove_group_participants? +

waha_remove_group_participants is provided by the WAHA MCP Server MCP server (seejux/waha-whatsapp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WAHA MCP Server tool call.

Start from WAHA MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →