google_ads_upload_customer_match

THE RISK

Medium Risk

Why google_ads_upload_customer_match needs a policy

Customer match uploads create or modify audience segments in Google Ads campaigns, which is reversible (audiences can be deleted or updated) and has financial impact potential since it affects ad targeting and campaign performance. This qualifies as Write rather than Execute (no arbitrary code execution) or Destructive (not irreversible).

From the tool's definition Tool name 'google_ads_upload_customer_match' indicates uploading customer match data to Google Ads. Customer match is a Google Ads feature that uploads customer lists (emails, phone numbers, etc.) to match against user accounts.

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

POLICY

How to control google_ads_upload_customer_match

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

policy.json

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

google_ads_upload_customer_match 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 MCP Server — 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 MCP Server tools

Financial google_ads_update_campaign_budget_v2 google_ads_update_campaign_budget_v2 Execute google_ads_custom_query google_ads_custom_query Write google_ads_batch_status_change google_ads_batch_status_change Write google_ads_add_audience_to_ad_group google_ads_add_audience_to_ad_group Write google_ads_add_audience_to_campaign google_ads_add_audience_to_campaign Write google_ads_add_call_extension google_ads_add_call_extension Write google_ads_add_callout_extension google_ads_add_callout_extension Write google_ads_add_campaign_exclusions google_ads_add_campaign_exclusions

All 142 Google Ads MCP Server 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 google_ads_upload_customer_match

What does the google_ads_upload_customer_match tool do? +

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

How do I enforce a policy on google_ads_upload_customer_match? +

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

What risk level is google_ads_upload_customer_match? +

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

Can I rate-limit google_ads_upload_customer_match? +

Yes. Add a rate_limit block to the google_ads_upload_customer_match 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 google_ads_upload_customer_match completely? +

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

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

Enforce policy on every Google Ads MCP Server tool call.

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.

CHECK YOUR STACK →