Get direct WhatsApp chat JID by contact phone number (less reliable, use get_chat_by_id if JID is known).
AI agents call get_direct_chat_by_contact_number to retrieve information from Mcp Whatsapp Web without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a lookup operation to retrieve a chat JID (identifier) from a phone number. It is a pure read operation with no side effects. The 'less reliable' note suggests it's a lookup utility. The blast radius of misuse is minimal - an attacker could enumerate chat identifiers but cannot access messages, modify data, execute code, or cause financial harm. Classified as Read with low severity.
From the tool's definition Tool description states 'Get direct WhatsApp chat JID by contact phone number' - it retrieves/queries a chat identifier based on input. No modification, deletion, execution, or financial operations are performed.
Documented attack patterns abuse exactly the kind of access get_direct_chat_by_contact_number gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Whatsapp Web, and nothing reaches the server without passing your rules. This is the rule we recommend for get_direct_chat_by_contact_number:
{
"version": "1",
"default": "deny",
"tools": {
"get_direct_chat_by_contact_number": {}
}
} get_direct_chat_by_contact_number is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get direct WhatsApp chat JID by contact phone number (less reliable, use get_chat_by_id if JID is known). It is categorised as a Read tool in the Mcp Whatsapp Web MCP Server, which means it retrieves data without modifying state.
Register the Mcp Whatsapp Web MCP server in PolicyLayer and add a rule for get_direct_chat_by_contact_number: 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 Mcp Whatsapp Web. Nothing to install.
get_direct_chat_by_contact_number 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_number 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_number. 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_number is provided by the Mcp Whatsapp Web MCP server (mario-andreschak/mcp-whatsapp-web). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Whatsapp Web, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Mcp Whatsapp Web tools catalogued and risk-classified — across an index of 43,000+ MCP servers.