AI agents call read_conversation to retrieve information from Wa Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical message data from a conversation without modifying, deleting, or executing any actions. It is a query-only operation that merely fetches and returns existing data. While WhatsApp conversations may contain sensitive personal information, the tool itself performs no destructive, write, execute, or financial operations.
From the tool's definition Tool name is 'read_conversation' and description states it 'Read message history for one conversation' and 'Returns most-recent messages first.' This is purely a retrieval operation with no side effects.
Attacks that exploit this kind of access
Read message history for one conversation. Returns most-recent messages first. Paginate older messages with the. It is categorised as a Read tool in the Wa Bridge MCP Server, which means it retrieves data without modifying state.
Register the Wa Bridge MCP server in PolicyLayer and add a rule for read_conversation: 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 Wa Bridge. Nothing to install.
read_conversation 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 read_conversation 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 read_conversation. 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.
read_conversation is provided by the Wa Bridge MCP server (obirimensah05/whatsapp-bridge). 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 →