A Guth Labs publication ↗
Back to News

Google Workspace’s agent OAuth cutoff has passed: check the client, not just the token

Google's previously announced OAuth transition for Workspace MCP integrations has passed its November 12 cutoff date. The company's October 12 release notes said rejection of requests from non-agent-designated OAuth clients would begin November 11. Clients not designated by November 12 would remain non-agentic; continuing MCP access would require a new client configured for an AI agent. Google did not specify an exact cutoff time or timezone in that notice. Google Workspace release notes

This is not a blanket shutdown of Workspace integrations. Google's notice excludes applications that only use Workspace REST APIs. For mixed applications, it directs developers to separate the agent client from the client supporting ordinary features. Release notes

The relevant setting is in Google Auth Platform's Clients section. Google's current configuration guide says to create a new OAuth client if an existing client's designation cannot be changed or if the existing client also supports non-agent features. The Chat MCP service remains a Developer Preview offering. Chat MCP configuration guide, updated November 5

Crucially, an agent label is not extra permission. Google says the designation does not add scopes or privileges; user consent and ordinary OAuth verification requirements still apply. Google's OAuth client management guidance

Why it matters for the fleet

Analysis: An agent can have a valid token and still encounter an integration failure if the identity behind that token is no longer eligible. That makes client classification worth checking before repeatedly refreshing credentials or blaming a model upgrade. Keep an inventory that distinguishes direct REST calls from MCP connections, with an owner for each client and a small read-only connectivity check.

Separating clients can also make failures easier to contain: an agent migration need not force the same change on a working human-facing application. This is a deployment planning recommendation, not evidence that Guth's systems are affected.

Verification and limits

The dated notice and two official implementation references were read directly. No live account was inspected, credentials changed, or requests tested. Independent operational confirmation of enforcement was not found. The exact time enforcement occurs, and whether a particular existing client can still be changed, must be checked in that account; the documentation alone does not establish either.

Sources and citations

Revision history

Published .