whatsapp_read_messages
Reads messages from a specific WhatsApp chat. The chat_id must come from a previous whatsapp_list_chats call. ⚠️ Uses Wacli (unofficial WhatsApp client). Accounts may be restricted for ToS violations.
This record as markdown: /tools/com-local-mcp-local-mcp/whatsapp-read-messages.md
What whatsapp_read_messages does on Local
AI agents call whatsapp_read_messages to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max messages to return (default 50) |
chat_id | string | Yes | Chat ID from whatsapp_list_chats |
Parameters from the server's own tool schema.
Why whatsapp_read_messages is rated Low
This tool retrieves and queries message data without modifying, deleting, or creating any content. It falls squarely into the Read category. Severity is medium (not low) because: (1) it accesses private communications, (2) the tool uses an unofficial WhatsApp client (Wacli) which violates ToS and could result in account restrictions, and (3) unrestricted access to all chat messages could expose sensitive information…
From the tool's definition Tool name explicitly includes 'read_messages' and description states 'Reads messages from a specific WhatsApp chat' with no mention of modification, deletion, or creation of data.
Attacks that exploit this kind of access
The rule that runs whatsapp_read_messages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For whatsapp_read_messages, this is the rule to start with:
whatsapp_read_messages is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every whatsapp_read_messages call is checked against it from then on.
Questions about whatsapp_read_messages
Reads messages from a specific WhatsApp chat. The chat_id must come from a previous whatsapp_list_chats call. ⚠️ Uses Wacli (unofficial WhatsApp client). Accounts may be restricted for ToS violations. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
whatsapp_read_messages accepts 2 parameters: limit, chat_id. Required: chat_id. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for whatsapp_read_messages: 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 Local. Nothing to install.
whatsapp_read_messages 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_read_messages 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_read_messages. 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_read_messages is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue