The platform binds long-lived refresh tokens cryptographically to a key, while short-lived access tokens remain standard Bearer tokens. Google says the design addresses infostealer malware and adversary-in-the-middle attacks. It also points developers to Google Cloud Secure Token Service (STS) for token delegation across multi-agent and Model Context Protocol workloads.
Implication: Teams can evaluate DPoP to reduce refresh-token replay exposure in Google OAuth integrations.
Thesis
Credential security for connected agents depends partly on constraining how reusable tokens can be replayed, not only on what an agent is instructed to do.
Observed facts
Mechanism
DPoP binds refresh tokens to a cryptographic key, making a copied token alone less useful for replay while leaving access tokens as Bearer tokens.
Why now
Google OAuth Platform has announced support, giving developers using its OAuth surface a concrete option as agent and MCP integrations require delegated credentials.
Implications
Teams can evaluate DPoP to reduce refresh-token replay exposure in Google OAuth integrations.
Delegated agent workflows still require careful assessment of access-token handling and end-to-end implementation.
Evidence boundary
The announcement describes the feature and intended threat mitigation, but supplies no adoption figures, independent validation, or measured reduction in compromises.
Watch conditions
Watch for implementation guidance, client-library support, and evidence about how DPoP behaves across real delegated agent workflows.