Overview dashboard of WhatsApp activity — message totals, top chats, top contacts, and group/DM breakdown. No arguments needed. Returns: - Totals: messages, contacts, chats, groups, DMs - Activity: messages today, this week - Top 5 chats by message count (name may be null for groups — use whatsap...
AI agents call whatsapp_stats to retrieve information from Waha without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval tool that queries and displays WhatsApp activity statistics. It has no side effects, does not modify or delete any data, and does not execute code or trigger external operations. The most severe related sibling tool (whatsapp_delete_message) is destructive, but this tool is strictly informational.
From the tool's definition Tool provides an "Overview dashboard of WhatsApp activity" with "message totals, top chats, top contacts, and group/DM breakdown." It retrieves and displays aggregated statistics without modifying, deleting, or executing actions.
Attacks that exploit this kind of access
Overview dashboard of WhatsApp activity — message totals, top chats, top contacts, and group/DM breakdown. No arguments needed. Returns: - Totals: messages, contacts, chats, groups, DMs - Activity: messages today, this week - Top 5 chats by message count (name may be null for groups — use whatsapp_get_contact to look up) - Top 5 contacts by message count. It is categorised as a Read tool in the Waha MCP Server, which means it retrieves data without modifying state.
Register the Waha MCP server in PolicyLayer and add a rule for whatsapp_stats: 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 Waha. Nothing to install.
whatsapp_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the whatsapp_stats 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 whatsapp_stats. 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.
whatsapp_stats is provided by the Waha MCP server (@marcos-heidemann/waha-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →