Remove a label from an ad group criterion.
AI agents use remove_label_from_criterion to create or update resources in Google Ads — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Ads environment.
Removing a label is a reversible modification (the label can be re-assigned), so it falls under Write rather than Destructive. The blast radius is medium since mislabeling criteria could affect campaign targeting and reporting, but the action is undoable.
From the tool's definition Remove a label from an ad group criterion
Documented attack patterns abuse exactly the kind of access remove_label_from_criterion gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Ads, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_label_from_criterion:
{
"version": "1",
"default": "deny",
"tools": {
"remove_label_from_criterion": {
"limits": [
{
"counter": "remove_label_from_criterion_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}remove_label_from_criterion stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Remove a label from an ad group criterion. It is categorised as a Write tool in the Google Ads MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Ads MCP server in PolicyLayer and add a rule for remove_label_from_criterion: 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. Nothing to install.
remove_label_from_criterion is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the remove_label_from_criterion 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 remove_label_from_criterion. 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.
remove_label_from_criterion is provided by the Google Ads MCP server (promobase/google-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Ads, 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.
59 Google Ads tools catalogued and risk-classified — across an index of 43,000+ MCP servers.