Supporting case
Google adds an identity requirement for agents connecting to Workspace
What happened
Google’s October 12 developer notice ↗ says that starting November 11 its Workspace Model Context Protocol servers will reject requests from apps whose authorization client is not marked as AI-powered. The protocol gives an agent a standard way to connect to external services; the OAuth client is the registered identity through which an app asks for permission. The change applies to this connector route, not every way to access Workspace. The notice also says clients left unmarked by November 12 need a new marked client, requiring developers to update the app. The exact time of enforcement and actual disruptions were not independently tested.
Google can now require apps on that route to identify themselves as agents, which can make agent use easier to distinguish and govern. The company still sets the conditions under which an outside agent can use the connector. A standard connection does not remove the underlying service’s authority to set access rules.
Dates and implementation stage
2026-11-11: Published commencement
