Search the Meta Ad Library by keyword or company name. For company searches, automatically resolves the company name to a Facebook page ID and fetches their ads. Supports filtering by country, status, media type, date range, and more. Use fetch_all: true to auto-paginate all results. Zero auth re...
AI agents call meta-search-ads to retrieve information from Ad Library MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes publicly available advertising data without side effects. It queries the Meta Ad Library (a public resource Meta provides for transparency) and returns results filtered by user parameters. No data is created, modified, deleted, or destroyed. No code execution or external operations are triggered beyond data retrieval.
From the tool's definition Tool performs search and retrieval operations on public Meta Ad Library data: 'Search the Meta Ad Library by keyword or company name' and 'fetch their ads'. Supports filtering and pagination but does not modify, delete, or execute operations.
Attacks that exploit this kind of access
Search the Meta Ad Library by keyword or company name. For company searches, automatically resolves the company name to a Facebook page ID and fetches their ads. Supports filtering by country, status, media type, date range, and more. Use fetch_all: true to auto-paginate all results. Zero auth required — this is public data. It is categorised as a Read tool in the Ad Library MCP MCP Server, which means it retrieves data without modifying state.
Register the Ad Library MCP server in PolicyLayer and add a rule for meta-search-ads: 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 Ad Library MCP. Nothing to install.
meta-search-ads 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-ads 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-ads. 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-ads is provided by the Ad Library MCP server (thedavidquan01/ad-library-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 →