Google bans programmatic proxies requiring direct Cloud project connections
Google has updated its Google Ads Developer Policies to explicitly prohibit programmatic proxies, including third-party hosted interfaces and Model Context Protocol servers, that act as intermediaries between advertisers and Google's systems. The policy mandates that all integrations must connect via a dedicated Google Cloud project to mitigate security risks like cross-tenant data leaks and performance bottlenecks.
Key Takeaways
- Policy explicitly bans Model Context Protocol (MCP) servers that wrap Google Ads capabilities for multiple independent businesses.
- Developers must now use per-entity Google authentication, ending headless programmatic account modifications without direct user sign-in.
- Internal-use tools and open-source software where users run code locally remain exempt from the new proxy restrictions.
- Non-compliance may result in downgraded API access levels or mandatory non-compliance fees according to the rate sheet.
Why It Matters
The prohibition of programmatic proxies forces a structural shift in how third-party ad tech and agentic AI tools interact with Google's ecosystem. By mandating dedicated Google Cloud projects, Google eliminates the shared infrastructure model that previously allowed smaller vendors to lower client setup hurdles at the cost of security transparency. This move aligns Google with broader industry efforts to govern the Model Context Protocol, which has become a primary vector for AI-driven campaign management. As Google's compliance team begins active reviews, the industry should watch for a consolidation of AI tool providers who can meet these heightened auditing and logging requirements.
Read full article at ppc.land
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source