AI agents call remove_custom_conversion_goal to permanently remove resources in Google Ads — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a conversion goal configuration. Once removed, the goal and its associated tracking/optimization data relationship is destroyed and cannot be automatically recovered without manual reconfiguration. This is a destructive action with potential business impact (loss of conversion tracking configuration), making it more severe than a Write operation but not Financial in nature.
From the tool's definition Tool name 'remove_custom_conversion_goal' uses 'remove', and the description states it removes (deletes) a custom conversion goal. Custom conversion goals are configuration objects that cannot be trivially restored.
Documented attack patterns abuse exactly the kind of access remove_custom_conversion_goal 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_custom_conversion_goal:
{
"version": "1",
"default": "deny",
"hide": [
"remove_custom_conversion_goal"
]
} remove_custom_conversion_goal disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a custom conversion goal. It is categorised as a Destructive tool in the Google Ads MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Ads MCP server in PolicyLayer and add a rule for remove_custom_conversion_goal: 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_custom_conversion_goal is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_custom_conversion_goal 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_custom_conversion_goal. 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_custom_conversion_goal 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.