Browse the FULL Meta targeting catalog for a class via /act_<id>/targetingbrowse?class=<class>. Use this when you want to enumerate everything Meta offers in a category (full behaviors taxonomy, all life events, every industry, etc.). For keyword-filtered search, use meta.targeting.account_search...
AI agents call meta.targeting.browse to retrieve information from Ads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates targeting taxonomy data (behaviors, life events, industries) from Meta's catalog without creating, modifying, or deleting any data. It is a read-only query operation with no side effects. The explicit distinction from 'search' tools and the use of 'browse' and 'enumerate' confirm it performs data retrieval only.
From the tool's definition Tool description uses 'Browse' and 'enumerate' language, queries the Meta targeting catalog via GET-style endpoint (/act_<id>/targetingbrowse?class=<class>), explicitly contrasts with search tools, and makes no mention of modification or deletion.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Browse the FULL Meta targeting catalog for a class via /act_<id>/targetingbrowse?class=<class>. Use this when you want to enumerate everything Meta offers in a category (full behaviors taxonomy, all life events, every industry, etc.). For keyword-filtered search, use meta.targeting.account_search or meta.targeting.search instead. It is categorised as a Read tool in the Ads MCP Server, which means it retrieves data without modifying state.
Register the Ads MCP server in PolicyLayer and add a rule for meta.targeting.browse: 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 Ads. Nothing to install.
meta.targeting.browse 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 meta.targeting.browse 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 meta.targeting.browse. 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.
meta.targeting.browse is provided by the Ads MCP server (manlikemuneeb/ads-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 →