google_ads_update_conversion_action
AI agents use google_ads_update_conversion_action to create or update resources in Google Ads MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Ads MCP Server environment.
Conversion actions are critical to Google Ads campaign configuration, affecting how conversions are tracked, attributed, and billed. Updating them is a Write operation (modifies campaign configuration reversibly) rather than Destructive (conversion actions can be re-edited).
From the tool's definition Tool name 'google_ads_update_conversion_action' indicates modification of conversion tracking configuration in Google Ads.
Documented attack patterns abuse exactly the kind of access google_ads_update_conversion_action 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 google_ads_update_conversion_action:
{
"version": "1",
"default": "deny",
"tools": {
"google_ads_update_conversion_action": {
"limits": [
{
"counter": "google_ads_update_conversion_action_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} google_ads_update_conversion_action 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.
google_ads_update_conversion_action. It is categorised as a Write tool in the Google Ads MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Ads MCP Server MCP server in PolicyLayer and add a rule for google_ads_update_conversion_action: 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.
google_ads_update_conversion_action 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 google_ads_update_conversion_action 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_update_conversion_action. 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_update_conversion_action is provided by the Google Ads MCP Server MCP server (johnoconnor0/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 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.
142 Google Ads MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.