AI agents call list_conversations 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 is a straightforward query operation that lists existing conversation metadata without side effects. While the data retrieved may be sensitive (conversation history), the tool itself performs only read-access retrieval. Severity is low because reading message metadata poses limited immediate risk compared to message manipulation, deletion, or financial operations.
From the tool's definition Tool 'list_conversations' retrieves and queries recent conversations with metadata (chat_jid, push_name, last message body and timestamp). No modification, deletion, or external action is performed—only data retrieval.
Attacks that exploit this kind of access
List recent conversations for a WhatsApp session, sorted by most recent message first. Each entry includes chat_jid, push_name, last message body and timestamp. 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 list_conversations: 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.
list_conversations 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 list_conversations 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 list_conversations. 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.
list_conversations 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 →