AI agents call search_contacts to retrieve information from WhatsApp Web MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations retrieve or query data without modifying state. The absence of description lowers confidence slightly, but the name and pattern among sibling tools (all Read category) strongly suggest this searches/queries contact data without side effects. If it performed contact creation/modification, it would be named differently (e.g., 'add_contact', 'update_contact').
From the tool's definition Tool name 'search_contacts' indicates a search operation; no description provided. Based on sibling tools context (get_chats, get_group_messages, get_messages) which are all Read operations, this follows the same pattern of information retrieval.
Documented attack patterns abuse exactly the kind of access search_contacts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WhatsApp Web MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_contacts:
{
"version": "1",
"default": "deny",
"tools": {
"search_contacts": {}
}
}search_contacts 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.
search_contacts. It is categorised as a Read tool in the WhatsApp Web MCP MCP Server, which means it retrieves data without modifying state.
Register the WhatsApp Web 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 Web MCP. 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 Web MCP server (pnizer/wweb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 WhatsApp Web MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 WhatsApp Web MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.