AI agents call get_recent_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 retrieves message data without modifying, deleting, or executing operations. However, severity is elevated to 'medium' rather than 'low' because: (1) WhatsApp messages often contain sensitive personal/business communication, payment details, or authentication codes; (2) bulk access to conversation history could expose private communications; (3) the tool's integration with webhooks means it has access to…
From the tool's definition Tool name 'get_recent_messages' and description states it 'Get recently received WhatsApp messages', which is a retrieval operation.
Attacks that exploit this kind of access
Get recently received WhatsApp messages. Unlike other MCP servers, this actually receives and stores incoming messages via webhooks. 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_recent_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_recent_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_recent_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_recent_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_recent_messages is provided by the Whatsapp MCP server (spirit122/whatsapp-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 →