google_ads_custom_query

THE RISK

High Risk

Why google_ads_custom_query needs a policy

The server description explicitly references 'custom GAQL queries', indicating this tool runs arbitrary user-supplied queries against Google Ads. GAQL can be used for both read and mutating operations depending on the query. Since the description is empty and the tool could execute arbitrary queries (including modifications), Execute is the most appropriate category.

From the tool's definition Tool name contains 'custom_query'; server description mentions 'custom GAQL queries' — GAQL (Google Ads Query Language) allows arbitrary query execution against Google Ads data and potentially mutating operations.

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

POLICY

How to control google_ads_custom_query

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "google_ads_custom_query": {
      "limits": [
        {
          "counter": "google_ads_custom_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

google_ads_custom_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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.

RATE-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 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 Write google_ads_add_keywords google_ads_add_keywords

All 142 Google Ads MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Google Ads MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about google_ads_custom_query

What does the google_ads_custom_query tool do? +

google_ads_custom_query. It is categorised as a Execute tool in the Google Ads MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on google_ads_custom_query? +

Register the Google Ads MCP Server MCP server in PolicyLayer and add a rule for google_ads_custom_query: 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_custom_query? +

google_ads_custom_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit google_ads_custom_query? +

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

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

google_ads_custom_query 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 →