AI agents call whatsapp_search_contacts to retrieve information from Wappmcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though whatsapp_search_contacts only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Search contacts by name, pushname, short name, number, or ID using query and optional limit parameters. It is categorised as a Read tool in the Wappmcp MCP Server, which means it retrieves data without modifying state.
Register the Wapp MCP server in PolicyLayer and add a rule for whatsapp_search_contacts: 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 Wappmcp. Nothing to install.
whatsapp_search_contacts 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_search_contacts 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_search_contacts. 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_search_contacts is provided by the Wapp MCP server (wappmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.