search_ad_targeting
Search Meta's ad-interest targeting catalog (returns interest ids + audience sizes). Use when designing a Meta ad draft and you need valid {id, name} targeting pairs for create_meta_ad_draft — e.g. search "pharmacy" or "compounding".
This record as markdown: /tools/com-getfreedomos-freedom-mcp/search-ad-targeting.md
What search_ad_targeting does on Freedom Mcp
AI agents call search_ad_targeting to retrieve information from Freedom Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Interest keyword, e.g. "pharmacy", "healthcare compliance" |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
Parameters from the server's own tool schema.
Why search_ad_targeting is rated Low
This tool queries Meta's ad-interest targeting catalog to retrieve metadata (interest IDs and audience sizes). It is purely informational—no data is created, modified, deleted, or executed. It supports the design phase of ad creation by providing lookup data. The actual ad creation is delegated to create_meta_ad_draft (a separate Write-category tool).
From the tool's definition Tool description states it 'returns interest ids + audience sizes' and is used for 'designing' and 'need[ing] valid {id, name} targeting pairs'. The verb 'search' and phrase 'returns' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs search_ad_targeting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_ad_targeting, this is the rule to start with:
search_ad_targeting is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every search_ad_targeting call is checked against it from then on.
Questions about search_ad_targeting
Search Meta's ad-interest targeting catalog (returns interest ids + audience sizes). Use when designing a Meta ad draft and you need valid {id, name} targeting pairs for create_meta_ad_draft — e.g. search "pharmacy" or "compounding". It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
search_ad_targeting accepts 2 parameters: query, companyId. Required: query, companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for search_ad_targeting: 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 Freedom Mcp. Nothing to install.
search_ad_targeting 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 search_ad_targeting 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 search_ad_targeting. 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.
search_ad_targeting is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue