22 tools. 7 can modify or destroy data without limits.
7 write tools that can modify data. Rate limits recommended.
Last updated:
Execute tools (gads_ad_group_performance, gads_campaign_performance, gads_device_performance) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
gads_account_info:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Google Ads server is primarily read-only with 15 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.
22 tools across 2 categories: Execute, Read. 15 are read-only. 7 can modify, create, or delete data.
One line change. Instead of running the Google Ads server directly, prefix it with Intercept: intercept -c google-ads.yaml -- npx -y @@zleventer/google-ads-mcp. Download a pre-built policy from policylayer.com/policies/google-ads and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.