Fallback: invoke any /customers/{id}/{resource}:mutate endpoint with raw operations. Use only when no named tool exists. Prefer google_ads.campaigns.pause/resume/update_budget. Requires confirm_passthrough=true. Dry-run by default.
AI agents invoke google_ads.passthrough.mutate to trigger actions in Ads. 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 is an Execute tool because it runs arbitrary operations against Google Ads API endpoints based on user-supplied arguments. Although mutations are involved (which might suggest Write), the true risk lies in the execution of unconstrained operations against a live ad account—the blast radius depends entirely on what operations the caller specifies.
From the tool's definition Tool invokes arbitrary '/customers/{id}/{resource}:mutate' endpoints with 'raw operations' via a generic passthrough mechanism.
Attacks that exploit this kind of access
Fallback: invoke any /customers/{id}/{resource}:mutate endpoint with raw operations. Use only when no named tool exists. Prefer google_ads.campaigns.pause/resume/update_budget. Requires confirm_passthrough=true. Dry-run by default. It is categorised as a Execute tool in the Ads MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ads MCP server in PolicyLayer and add a rule for google_ads.passthrough.mutate: 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 Ads. Nothing to install.
google_ads.passthrough.mutate 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 google_ads.passthrough.mutate 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 google_ads.passthrough.mutate. 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.
google_ads.passthrough.mutate is provided by the Ads MCP server (manlikemuneeb/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 →