AI agents call wa_business_owned_wabas 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 queries and retrieves existing business account data without modifying, executing operations, or causing side effects. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The blast radius of misuse is minimal since exposure would only grant visibility into business account metadata.
From the tool's definition Tool performs a GET request to retrieve WhatsApp Business Accounts (WABAs) owned by a business. The description explicitly states it 'returns' data with no modification or deletion capability. The HTTP method is GET, a read-only operation.
Attacks that exploit this kind of access
GET /{business_id}/owned_whatsapp_business_accounts — returns WABAs owned by the parent Business. 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_business_owned_wabas: 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_business_owned_wabas 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_business_owned_wabas 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_business_owned_wabas. 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_business_owned_wabas 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 →