Search for interest-based targeting options.
AI agents call search_interests to retrieve information from KonQuest Meta Ads MCP 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 available interest-based targeting options from Meta's advertising system. It returns matching interests to support campaign targeting configuration, but does not create, modify, delete, or execute any operations. It has no blast radius if misused by an agent—at worst, it returns a list of interests. This is a classic Read operation.
From the tool's definition Tool name and description: 'Search for interest-based targeting options.' The verb 'search' and the action of querying targeting options indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Search for interest-based targeting options. It is categorised as a Read tool in the KonQuest Meta Ads MCP MCP Server, which means it retrieves data without modifying state.
Register the KonQuest Meta Ads MCP server in PolicyLayer and add a rule for search_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 KonQuest Meta Ads MCP. Nothing to install.
search_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 search_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 search_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.
search_interests is provided by the KonQuest Meta Ads MCP server (brandu-mos/konquest-meta-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 →