Following the launch of new agent tools like the Google Workspace MCP server,
we are introducing a standardized tiering model for Google Workspace APIs,
including MCP, to safeguard the ecosystem while fostering innovation. This model
provides a predictable path to scale for high-impact applications and protects
against unique risks such as API abuse and unintended large-scale data egress.
We expect that less than 1% of active developers will need to move beyond the
standard usage tier, ensuring the vast majority of our community can continue to
build without friction.

- As of May 1, 2026, we are adjusting usage quotas across several
  Google Workspace product APIs, starting with Gmail API,
  Google Calendar API, and Google Drive API. These adjustments are designed to more
  closely align with typical usage patterns for common use cases, ensuring
  that the platform helps support safety, and privacy that
  Google Workspace users and customers expect.

  <br />

  | Existing projects using affected APIs between November 2025 and April 2026 | New projects (without prior use of APIs) from May 1, 2026 |
  |---|---|
  | API usage quotas already in place will remain unchanged for at least 60 days. | New API usage quotas documented for [Gmail API](https://developers.google.com/workspace/gmail/api/reference/quota), [Calendar API](https://developers.google.com/workspace/calendar/api/guides/quota), and [Drive API](https://developers.google.com/workspace/drive/api/guides/limits) will be rolled out over several weeks, applying to any project created from May 1, 2026. |
  | Requests to increase quotas can be submitted for approval as per the details for each API. ||
  | Later in 2026, following 90 days of notice: - Quota increase requests will require Google Cloud billing to be enabled. - API usage *over* standard daily thresholds will generate charges on your Google Cloud bill. - New standard API quotas will apply unless an increased quota has already been approved and billing is enabled. ||

  <br />

- More details regarding initial changes to API usage quotas are available for
  [Gmail API](https://developers.google.com/workspace/gmail/api/reference/quota), [Calendar API](https://developers.google.com/workspace/calendar/api/guides/quota), or [Drive API](https://developers.google.com/workspace/drive/api/guides/limits).

## Coming soon: Faster access for scaled usage to our tools

For developers who will require faster, scaled access we plan to introduce an
option for projects to increase their standard usage quotas through a paid
option. Projects implementing the Google Workspace APIs will have the ability
to increase their project quotas by agreeing to pay for API usage above the
standard daily limit. We expect to provide this billable usage quota increase
option with added details in the coming months, with 90 days notice.

## Google Workspace developer policy and Google terms

Note that working with Google Workspace APIs is still subject to the [Google Workspace API developer
policy](https://developers.google.com/workspace/workspace-api-user-data-developer-policy) and the [Google
APIs Terms of Service](https://developers.google.com/terms). As such, Google may
require verification, such as in the form of an audit, of adherence to our user
data policies.

## Related topics

- [Configure the Google Workspace MCP servers](https://developers.google.com/workspace/guides/configure-mcp-servers)
- Blog announcement: [Agent tools and security updates for Google Workspace
  developers](http://workspaceupdates.googleblog.com/2026/05/agent-tools-and-security-updates-for-workspace-developers.html).