List recent WhatsApp conversations with contact name, last message, and unread count.
AI agents call whatsapp_list_conversations to retrieve information from VIDA AI WhatsApp MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool exclusively performs data retrieval: it lists conversations and returns metadata (contact names, last messages, unread counts) without creating, modifying, deleting, or executing anything.
From the tool's definition Tool 'whatsapp_list_conversations' retrieves and displays recent WhatsApp conversations with contact name, last message, and unread count—a pure query operation with no side effects or data modification.
Attacks that exploit this kind of access
List recent WhatsApp conversations with contact name, last message, and unread count. It is categorised as a Read tool in the VIDA AI WhatsApp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VIDA AI WhatsApp MCP Server MCP server in PolicyLayer and add a rule for whatsapp_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 VIDA AI WhatsApp MCP Server. Nothing to install.
whatsapp_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 whatsapp_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 whatsapp_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.
whatsapp_list_conversations is provided by the VIDA AI WhatsApp MCP Server MCP server (juancvergara1/vidaai-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 →