Resolve a contact by name or phone number and return the chat metadata.
AI agents call get_chat_by_contact to retrieve information from WhatsApp MCP Stream without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing chat data indexed by contact identifier (name or phone number). It performs a lookup that does not alter any state, execute commands, or incur financial consequences. The lowest-severity Read category applies.
From the tool's definition Tool returns 'chat metadata' after resolving a contact—a retrieval operation with no modification or side effects. The description explicitly indicates read-only behavior: 'resolve...and return.'
Attacks that exploit this kind of access
Resolve a contact by name or phone number and return the chat metadata. It is categorised as a Read tool in the WhatsApp MCP Stream MCP Server, which means it retrieves data without modifying state.
Register the WhatsApp MCP Stream MCP server in PolicyLayer and add a rule for get_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 Stream. Nothing to install.
get_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_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_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_chat_by_contact is provided by the WhatsApp MCP Stream MCP server (loglux/whatsapp-mcp-stream). 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 →