Get a readable summary of recent messages in a WhatsApp chat, including sender names and timestamps. This is optimized for readability — use whatsapp_read_messages for structured data with filtering, or whatsapp_search_messages for full-text search. Args: - contactId: Phone digits for a person, or
AI agents call whatsapp_chat_summary 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 tool retrieves and summarizes existing WhatsApp chat data. It performs no creation, modification, deletion, code execution, or financial operations. The primary action is reading message content from a chat history, which is a non-destructive information retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description explicitly states 'Get a readable summary of recent messages' and recommends 'whatsapp_read_messages for structured data' and 'whatsapp_search_messages for full-text search', indicating this is a query/retrieval operation with no modification…
Attacks that exploit this kind of access
Get a readable summary of recent messages in a WhatsApp chat, including sender names and timestamps. This is optimized for readability — use whatsapp_read_messages for structured data with filtering, or whatsapp_search_messages for full-text search. Args: - contactId: Phone digits for a person, or. 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_chat_summary: 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_chat_summary 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_chat_summary 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_chat_summary. 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_chat_summary 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 →