Amazon Cognito supports OAuth 2.0 token exchange (RFC 8693): agents acting for a user swap to a narrower token for each downstream service
A standard token pattern for agents acting on a user's behalf. What limits the exchanged token carries, and how downstream services tell an agent from the user.
// Key points
- A service or agent can exchange a user's token for a new one scoped to a specific downstream service: narrower than the original, bound to a single audience, and without a refresh token.
- With an actor token, Cognito adds an act claim identifying the intermediary, so downstream services can tell an agent's request from the user's own; the example given is an MCP server exchanging for a narrow token to call a backend API.
- It works through the token endpoint or the new GetDerivedToken API, on the Essentials and Plus feature plans in all Regions where Cognito is available.
Builder's takeMany MCP servers today pass the user's original token all the way down, which over-grants access and makes it hard to tell who did what. Teams on Cognito can switch to token exchange directly; others should still follow the RFC 8693 pattern: exchange for a narrow token at each hop and log the act claim.
// Background · from #AI agents
Full timeline →- Nov 14 OpenAI introduces ChatGPT Wallet: agents in ChatGPT Work, Codex and dots can complete purchases with user approval
- Nov 14 Cloudflare: requests from AI penetration testing orchestrators are up 30x since October 1, with 50+ framework families scanning its customers in three days
- Nov 14 Cloudflare open-sources Kitesurf under Apache 2.0: a browser for AI agents that runs on Workers with no browser container