REQUIRED for analyzing video ads from Google. Download and analyze ad videos using Gemini
AI agents invoke analyze_ad_video to trigger actions in Google Ads MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs two active operations: downloading external video content and running it through an AI model (Gemini) for analysis. These are external operations with side effects (network requests, API calls, potential media caching), placing it in the Execute category.
From the tool's definition Download and analyze ad videos using Gemini — triggers external operations: downloading video content and executing AI analysis via Gemini model
Documented attack patterns abuse exactly the kind of access analyze_ad_video 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 analyze_ad_video:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_ad_video": {
"limits": [
{
"counter": "analyze_ad_video_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} analyze_ad_video stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
REQUIRED for analyzing video ads from Google. Download and analyze ad videos using Gemini. It is categorised as a Execute tool in the Google Ads MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Google Ads MCP Server MCP server in PolicyLayer and add a rule for analyze_ad_video: 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.
analyze_ad_video is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the analyze_ad_video 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 analyze_ad_video. 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.
analyze_ad_video 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.