Get list of all WhatsApp chats.
AI agents call whatsapp_get_chats to retrieve information from WSAPI WhatsApp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing chat data without creating, modifying, deleting, or executing any operations. It is a read-only operation with minimal security risk—it exposes chat metadata but does not alter state. Severity is low because while unauthorized access to chat lists could be a privacy concern, the tool itself performs no dangerous actions.
From the tool's definition Tool name and description indicate 'Get list' operation with no modification or side effects. The verb 'get' and phrase 'list of all WhatsApp chats' clearly indicate data retrieval.
Attacks that exploit this kind of access
Get list of all WhatsApp chats. It is categorised as a Read tool in the WSAPI WhatsApp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WSAPI WhatsApp MCP Server MCP server in PolicyLayer and add a rule for whatsapp_get_chats: 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 WSAPI WhatsApp MCP Server. Nothing to install.
whatsapp_get_chats 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_get_chats 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_get_chats. 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_get_chats is provided by the WSAPI WhatsApp MCP Server MCP server (wsapi-chat/wsapi-mcp). 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 →