AI agents use update_customer_asset_status 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.
This tool modifies the status of customer assets in Google Ads, which is a reversible write operation. While the description is empty (lowering confidence slightly), the name and server context indicate it updates asset status fields. This is Write rather than Execute because it modifies specific data attributes rather than triggering arbitrary external operations.
From the tool's definition Tool name 'update_customer_asset_status' indicates modification of asset status within Google Ads customer account. Server context shows this wraps Google Ads API v20 for managing campaigns, budgets, and related entities.
Documented attack patterns abuse exactly the kind of access update_customer_asset_status 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 update_customer_asset_status:
{
"version": "1",
"default": "deny",
"tools": {
"update_customer_asset_status": {
"limits": [
{
"counter": "update_customer_asset_status_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_customer_asset_status 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.
update_customer_asset_status. 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 update_customer_asset_status: 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.
update_customer_asset_status 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 update_customer_asset_status 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 update_customer_asset_status. 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.
update_customer_asset_status 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.