AI agents call get_contacts_list to retrieve information from Wati without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name contains the verb 'get', which is a hallmark of read-only retrieval operations. No side effects, modifications, deletions, or external triggers are implied.
From the tool's definition Tool name 'get_contacts_list' indicates a retrieval operation consistent with sibling tools like 'get_messages' and 'get_media_by_filename' which are read-only query operations.
Attacks that exploit this kind of access
get_contacts_list. It is categorised as a Read tool in the Wati MCP Server, which means it retrieves data without modifying state.
Register the Wati MCP server in PolicyLayer and add a rule for get_contacts_list: 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 Wati. Nothing to install.
get_contacts_list 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_contacts_list 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_contacts_list. 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_contacts_list is provided by the Wati MCP server (jairajmehra/wati_whatsapp_mcp). 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 →