zernio_remove_whatsapp_group_participants

Remove participants from a WhatsApp Group.

SERVERZernio SOURCEeyalm321/zernio-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eyalm321-zernio-mcp/zernio-remove-whatsapp-group-participants.md

What zernio_remove_whatsapp_group_participants does on Zernio

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

Why zernio_remove_whatsapp_group_participants is rated Critical

Removing participants from a WhatsApp group is an irreversible action from the participant's perspective — they are expelled from the group and lose access to its history and ongoing communications. This cannot be easily undone without re-adding each participant. The blast radius is high as it could affect many users simultaneously if misused.

From the tool's definition Remove participants from a WhatsApp Group

Questions about zernio_remove_whatsapp_group_participants

What does the zernio_remove_whatsapp_group_participants tool do? +

Remove participants from a WhatsApp Group. It is categorised as a Destructive tool in the Zernio 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 zernio_remove_whatsapp_group_participants? +

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

What risk level is zernio_remove_whatsapp_group_participants? +

zernio_remove_whatsapp_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 zernio_remove_whatsapp_group_participants? +

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

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

zernio_remove_whatsapp_group_participants is provided by the Zernio MCP server (eyalm321/zernio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Zernio, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Zernio's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.