AI agents use add_participants_to_group to create or update resources in WhatsApp Web MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WhatsApp Web MCP environment.
This tool creates or modifies group membership data by adding participants to an existing group. While reversible (participants can be removed), it alters group composition and permissions, affecting who has access to group communications.
From the tool's definition Tool name 'add_participants_to_group' indicates modification of group membership. Description is empty, but sibling tools include 'create_group' and 'get_group_by_id', establishing this server's domain as group management.
Documented attack patterns abuse exactly the kind of access add_participants_to_group gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WhatsApp Web MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add_participants_to_group:
{
"version": "1",
"default": "deny",
"tools": {
"add_participants_to_group": {
"limits": [
{
"counter": "add_participants_to_group_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_participants_to_group 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.
Free to start. No card required.
add_participants_to_group. It is categorised as a Write tool in the WhatsApp Web MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WhatsApp Web MCP server in PolicyLayer and add a rule for add_participants_to_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 WhatsApp Web MCP. Nothing to install.
add_participants_to_group 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 add_participants_to_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.
Set action: deny in the PolicyLayer policy for add_participants_to_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.
add_participants_to_group is provided by the WhatsApp Web MCP server (pnizer/wweb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 WhatsApp Web MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 WhatsApp Web MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.