Critical Risk →

remove_group_participant

Remove a participant from a WhatsApp group

How to control remove_group_participant ↓

What remove_group_participant does on Mcp Ap2

AI agents call remove_group_participant to permanently remove resources in Mcp Ap2 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why remove_group_participant needs a policy

Removing a participant from a group cannot be undone automatically; the user loses access to the group and its history. This constitutes an irreversible modification to group membership, classifying it as Destructive. Severity is high because it affects real user access and communication channels at scale if misused by an AI agent.

From the tool's definition 'Remove a participant from a WhatsApp group' — removing a participant is an irreversible action that revokes group membership and access

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

How to control remove_group_participant

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

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

remove_group_participant 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 Mcp Ap2 — 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 remove_group_participant

What does the remove_group_participant tool do? +

Remove a participant from a WhatsApp group. It is categorised as a Destructive tool in the Mcp Ap2 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 remove_group_participant? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for remove_group_participant: 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 Mcp Ap2. Nothing to install.

What risk level is remove_group_participant? +

remove_group_participant 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 remove_group_participant? +

Yes. Add a rate_limit block to the remove_group_participant 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 remove_group_participant completely? +

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

remove_group_participant is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, 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.

1300 Mcp Ap2 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.