AI agents use send_group_message 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 writes/creates data (messages) with side effects that are reversible but significant. While messages can theoretically be deleted, once sent they exist in recipient inboxes and notification systems, creating real communication that cannot be fully undone. It does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial).
From the tool's definition Tool name 'send_group_message' indicates it sends messages to groups. The server description states it enables 'automated messaging' and 'group chat functionality.' Sending messages creates new data (message records) with persistent effects in recipient…
Documented attack patterns abuse exactly the kind of access send_group_message 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 send_group_message:
{
"version": "1",
"default": "deny",
"tools": {
"send_group_message": {
"limits": [
{
"counter": "send_group_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_group_message 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.
send_group_message. 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 send_group_message: 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.
send_group_message 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 send_group_message 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 send_group_message. 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.
send_group_message 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.