AI agents use send_message to create or update resources in WhatsApp MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WhatsApp MCP Server environment.
Sending messages modifies WhatsApp state by creating new message records, but the action is reversible (messages can be deleted). This is a Write operation rather than Execute because it doesn't run arbitrary code or trigger unpredictable external operations—it performs a specific, bounded communication action.
From the tool's definition Tool name 'send_message' combined with server description stating it 'enabling them to...send messages via WhatsApp' indicates the tool creates and sends messages, a reversible write operation.
Documented attack patterns abuse exactly the kind of access send_message gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WhatsApp MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_message:
{
"version": "1",
"default": "deny",
"tools": {
"send_message": {
"limits": [
{
"counter": "send_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_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_message. It is categorised as a Write tool in the WhatsApp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WhatsApp MCP Server MCP server in PolicyLayer and add a rule for send_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 MCP Server. Nothing to install.
send_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_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_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_message is provided by the WhatsApp MCP Server MCP server (jlucaso1/whatsapp-mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WhatsApp MCP Server, 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.
7 WhatsApp MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.