Get WhatsApp chat metadata by sender phone number.
AI agents call get_direct_chat_by_contact to retrieve information from WhatsApp MCP Automation without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation—it queries and retrieves existing chat metadata without creating, modifying, or deleting data. Severity is high because unauthorized access to WhatsApp chat metadata could expose private conversations, phone numbers, contact relationships, and communication patterns of individuals without their consent.
From the tool's definition Tool name 'get_direct_chat_by_contact' and description 'Get WhatsApp chat metadata by sender phone number' explicitly retrieves chat data without modification.
Attacks that exploit this kind of access
Get WhatsApp chat metadata by sender phone number. It is categorised as a Read tool in the WhatsApp MCP Automation MCP Server, which means it retrieves data without modifying state.
Register the WhatsApp MCP Automation MCP server in PolicyLayer and add a rule for get_direct_chat_by_contact: 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 MCP Automation. Nothing to install.
get_direct_chat_by_contact 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_direct_chat_by_contact 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_direct_chat_by_contact. 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_direct_chat_by_contact is provided by the WhatsApp MCP Automation MCP server (priyasogani8-star/whatsapp-mcp-automation). 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 →