Critical Risk →

waha_leave_group

Leave a group.

How to control waha_leave_group ↓

What waha_leave_group does on WAHA MCP Server

AI agents call waha_leave_group to permanently remove resources in WAHA MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why waha_leave_group needs a policy

Leaving a group is a one-way, irreversible action: once the agent leaves, it loses access to the group chat, its history, and membership. There is no 'undo' — rejoining requires a new invite link or admin approval. This matches the Destructive category due to the permanent and unrecoverable nature of the action.

From the tool's definition 'Leave a group' — permanently exits the agent from a WhatsApp group, which is an irreversible action (cannot rejoin without a new invitation).

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

How to control waha_leave_group

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_leave_group:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "waha_leave_group"
  ]
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about waha_leave_group

What does the waha_leave_group tool do? +

Leave a group. 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_leave_group? +

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

What risk level is waha_leave_group? +

waha_leave_group 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_leave_group? +

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

How do I block waha_leave_group completely? +

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

What MCP server provides waha_leave_group? +

waha_leave_group 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.

Free to start. No card required.

52 WAHA MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.