Search WhatsApp contacts by name or phone number.
AI agents call search_contacts 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.
Searching contacts retrieves existing contact data without altering, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could enumerate contacts but cannot harm systems, delete data, or trigger financial/destructive actions. Classification as Read is appropriate.
From the tool's definition Tool name is 'search_contacts' and description states it 'Search[es] WhatsApp contacts by name or phone number.' This is a query operation with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Search WhatsApp contacts by name or 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 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 WhatsApp MCP Automation. Nothing to install.
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 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 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.
search_contacts 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 →