AI agents call wa_phone_numbers to retrieve information from Meta without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves phone number information from WhatsApp Business API via a GET request with no side effects. It is a straightforward data retrieval operation consistent with the Read category. The read-only nature of the server and the GET HTTP method confirm there is no ability to modify or execute operations.
From the tool's definition Tool name 'wa_phone_numbers' and description 'GET /{waba_id}/phone_numbers' indicate a GET request to retrieve phone number data. Server is explicitly described as 'Read-only MCP server'. No modification, deletion, or execution capability.
Attacks that exploit this kind of access
GET /{waba_id}/phone_numbers. It is categorised as a Read tool in the Meta MCP Server, which means it retrieves data without modifying state.
Register the Meta MCP server in PolicyLayer and add a rule for wa_phone_numbers: 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 Meta. Nothing to install.
wa_phone_numbers 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 wa_phone_numbers 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 wa_phone_numbers. 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.
wa_phone_numbers is provided by the Meta MCP server (nourpups/meta-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 →