Get detailed information about a specific Google ad including variations, regional stats, and impressions. Use this tool with the adUrl from get_google_ads to retrieve full ad details including all text variations, image URLs, headlines, and descriptions. Essential for analyzing ad content and ex...
AI agents call get_google_ad_details to retrieve information from Google Ads MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves public ad database records. It has no side effects: it does not create, modify, delete, or execute anything. The data source is Google's public ads database, which is designed for research and transparency. The blast radius of misuse is minimal—an agent could over-query the service or retrieve excessive data, but cannot corrupt or destroy information.
From the tool's definition Tool description states 'Get detailed information about a specific Google ad' and 'retrieve full ad details including all text variations, image URLs, headlines, and descriptions.' The verb is 'Get' and the action is retrieval only—no modification, deletion,…
Documented attack patterns abuse exactly the kind of access get_google_ad_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Ads MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_google_ad_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_google_ad_details": {}
}
} get_google_ad_details 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.
Get detailed information about a specific Google ad including variations, regional stats, and impressions. Use this tool with the adUrl from get_google_ads to retrieve full ad details including all text variations, image URLs, headlines, and descriptions. Essential for analyzing ad content and extracting media URLs for visual analysis. It is categorised as a Read tool in the Google Ads MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Ads MCP Server MCP server in PolicyLayer and add a rule for get_google_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 Google Ads MCP Server. Nothing to install.
get_google_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_google_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_google_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_google_ad_details is provided by the Google Ads MCP Server MCP server (proxy-intell/google-ads-library-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Ads 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.
7 Google Ads MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.