mutate_conversion_goal_campaign_configs

THE RISK

Medium Risk

Why mutate_conversion_goal_campaign_configs needs a policy

The tool modifies campaign-linked conversion goal configurations, which are reversible but critical to ad campaign performance and measurement. This is a Write operation rather than Destructive because configuration changes can typically be reverted. Severity is high due to impact on campaign analytics, conversion tracking, and potentially budget/ROI decisions.

From the tool's definition Tool name 'mutate_conversion_goal_campaign_configs' indicates modification of conversion goal configurations tied to campaigns. The prefix 'mutate' is standard Google Ads API terminology for write operations.

Documented attack patterns abuse exactly the kind of access mutate_conversion_goal_campaign_configs gives an agent:

POLICY

How to control mutate_conversion_goal_campaign_configs

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 mutate_conversion_goal_campaign_configs:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mutate_conversion_goal_campaign_configs": {
      "limits": [
        {
          "counter": "mutate_conversion_goal_campaign_configs_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

mutate_conversion_goal_campaign_configs 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.

Create a free account and register Google Ads — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Google Ads tools

Destructive remove_ad_group_customizer Remove an ad group customizer. Destructive remove_asset_group_signal Remove an asset group signal. Destructive remove_custom_conversion_goal Remove a custom conversion goal. Destructive remove_customer_asset Remove a customer asset. Destructive remove_customer_customizer Remove a customer customizer. Destructive remove_experiment_arm Remove an experiment arm. Destructive remove_keyword_plan_ad_group Remove a keyword plan ad group. Destructive remove_keyword_plan_ad_group_keyword Remove a keyword plan ad group keyword.

All 59 Google Ads tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about mutate_conversion_goal_campaign_configs

What does the mutate_conversion_goal_campaign_configs tool do? +

mutate_conversion_goal_campaign_configs. 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.

How do I enforce a policy on mutate_conversion_goal_campaign_configs? +

Register the Google Ads MCP server in PolicyLayer and add a rule for mutate_conversion_goal_campaign_configs: 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.

What risk level is mutate_conversion_goal_campaign_configs? +

mutate_conversion_goal_campaign_configs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mutate_conversion_goal_campaign_configs? +

Yes. Add a rate_limit block to the mutate_conversion_goal_campaign_configs 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.

How do I block mutate_conversion_goal_campaign_configs completely? +

Set action: deny in the PolicyLayer policy for mutate_conversion_goal_campaign_configs. 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.

What MCP server provides mutate_conversion_goal_campaign_configs? +

mutate_conversion_goal_campaign_configs 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.

Enforce policy on every Google Ads tool call.

Start from Google Ads, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →