get_ad_details
AI agents call get_ad_details to retrieve information from Meta 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 publicly available ad library metadata (advertiser, ad copy, reach statistics) without side effects. It is a pure read operation that queries existing data. The empty description for this specific tool is supplemented by the server context showing ad library search/retrieval functionality. Severity is low because the data returned is public and read-only with minimal blast radius if misused.
From the tool's definition Server description states it 'searches the Meta (Facebook) Ad Library' and 'returns ad details including advertiser, ad copy, and EU reach.' The tool name 'get_ad_details' and sibling tool 'search_ads' indicate querying/retrieval operations.
Attacks that exploit this kind of access
get_ad_details. It is categorised as a Read tool in the Meta Ad Library MCP MCP Server, which means it retrieves data without modifying state.
Register the Meta Ad Library MCP server in PolicyLayer and add a rule for get_ad_details: 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 Ad Library MCP. Nothing to install.
get_ad_details 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 get_ad_details 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 get_ad_details. 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.
get_ad_details is provided by the Meta Ad Library MCP server (konstantin-tradient/meta-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 →