Searches for interest-based targeting options for ad sets. Args: - q (string): Search query (e.g.,
AI agents call meta_search_targeting_interests to retrieve information from Meta MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries targeting interest data from Meta's ad platform to help construct ad targeting parameters. It has no side effects—it does not create, modify, delete, or execute any actions. It is a pure read operation that returns search results.
From the tool's definition Tool name contains 'search' and description states it 'Searches for interest-based targeting options' with no indication of data modification, deletion, or execution of external operations. The argument is a search query string.
Documented attack patterns abuse exactly the kind of access meta_search_targeting_interests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_search_targeting_interests:
{
"version": "1",
"default": "deny",
"tools": {
"meta_search_targeting_interests": {}
}
} meta_search_targeting_interests 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.
Searches for interest-based targeting options for ad sets. Args: - q (string): Search query (e.g.,. It is categorised as a Read tool in the Meta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_search_targeting_interests: 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 MCP Server. Nothing to install.
meta_search_targeting_interests 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_search_targeting_interests 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_search_targeting_interests. 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_search_targeting_interests is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meta MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.