AI agents call search_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 and queries message content without creating, modifying, deleting, or executing operations. It returns excerpts for search results only. The read-only nature of the server and the explicit search/query semantics place this firmly in the Read category. Low severity due to the constraints of local-only operation and inability to trigger side effects.
From the tool's definition Tool description explicitly states 'Search message bodies via local full-text search. Returns chat_id + message excerpts.' The action is querying/searching existing data with no modification capability. Server description emphasizes 'read-only interface.'
Attacks that exploit this kind of access
Search message bodies via local full-text search. Returns chat_id + message excerpts. 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 search_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.
search_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 search_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 search_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.
search_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 →