AI agents use create_customer_customizer 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.
The 'create_' prefix and context from sibling tools establish this as a data creation/modification operation. Creating a customer customizer modifies customer account configuration reversibly, fitting the Write category. Severity is medium because misuse could create unwanted customizations affecting ad campaigns but can be reversed by deletion.
From the tool's definition Tool name 'create_customer_customizer' indicates creation of a customizer resource within Google Ads customer account, consistent with sibling tools like 'create_ad_group_customizer', 'create_audience_signal', and 'create_custom_conversion_goal' which are all…
Documented attack patterns abuse exactly the kind of access create_customer_customizer 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 create_customer_customizer:
{
"version": "1",
"default": "deny",
"tools": {
"create_customer_customizer": {
"limits": [
{
"counter": "create_customer_customizer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_customer_customizer 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.
create_customer_customizer. 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 create_customer_customizer: 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.
create_customer_customizer 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 create_customer_customizer 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 create_customer_customizer. 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.
create_customer_customizer 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.