AI agents call get_chat_messages to retrieve information from Whatsapp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only—it fetches existing messages and their metadata without side effects. It cannot modify, delete, or create data. The read-only nature of the server further confirms this classification. Risk is low because the blast radius of accessing chat messages depends on data sensitivity (which is mitigated by local-only operation and explicit user context), not operational damage.
From the tool's definition Tool description explicitly states 'Read messages from a chat (text + metadata)' and the server is described as providing a 'read-only interface to WhatsApp'. The tool retrieves chat message data without modification, creation, or deletion.
Attacks that exploit this kind of access
Read messages from a chat (text + metadata). Use chat_id from list_chats. Most recent first. It is categorised as a Read tool in the Whatsapp MCP Server, which means it retrieves data without modifying state.
Register the Whatsapp MCP server in PolicyLayer and add a rule for get_chat_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 Whatsapp. Nothing to install.
get_chat_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 get_chat_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 get_chat_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.
get_chat_messages is provided by the Whatsapp MCP server (joaohts/whatsapp-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 →