zernio_add_whatsapp_group_participants
Add participants to an existing WhatsApp Group.
This record as markdown: /tools/eyalm321-zernio-mcp/zernio-add-whatsapp-group-participants.md
What zernio_add_whatsapp_group_participants does on Zernio
AI agents use zernio_add_whatsapp_group_participants to create or update resources in Zernio, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zernio environment.
Why zernio_add_whatsapp_group_participants is rated Medium
This tool performs a reversible modification operation (adding participants to a group). It does not execute arbitrary code, delete data, move money, or cause irreversible harm. The primary risk is that an agent could add unintended users to groups without authorization, potentially causing communication disruption or privacy issues, but the operation itself is reversible (participants can be removed).
From the tool's definition The tool name and description indicate it 'Add participants to an existing WhatsApp Group' — this is a write operation that modifies group membership by adding users. It creates new associations/relationships within WhatsApp groups.
Attacks that exploit this kind of access
The rule that runs zernio_add_whatsapp_group_participants safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zernio, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zernio_add_whatsapp_group_participants, this is the rule to start with:
zernio_add_whatsapp_group_participants stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Zernio, apply this rule, and every zernio_add_whatsapp_group_participants call is checked against it from then on.
Questions about zernio_add_whatsapp_group_participants
Add participants to an existing WhatsApp Group. It is categorised as a Write tool in the Zernio MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zernio MCP server in PolicyLayer and add a rule for zernio_add_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.
zernio_add_whatsapp_group_participants is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zernio_add_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.
Set action: deny in the PolicyLayer policy for zernio_add_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.
zernio_add_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.
This server
Across the catalogue