Protocol

Check the authority a scoped token actually grants

Requesting narrow access is only the first half of the job. The issuer must grant it, and the receiving service must enforce it.

About 2 min read

Before you use it

Use when
  • An agent currently receives a long-lived API key with more authority than the current task requires.

Keep this limit in mind

  • Scoped tokens are not a substitute for authorization design, audit or human approval where the impact requires it.

Current editorial reading

Start with permissions the service understands

Where token exchange is supported, request access for the required resource and operation, with a short lifetime appropriate to the task. Check the issued scope and expiry instead of assuming the request was granted unchanged. Keep approval and policy outside the model. Do not invent a task-level permission that the receiving service cannot enforce.

Keep the broad credential out of reach

For a triage agent, test that reading the allowed ticket succeeds while an out-of-scope write is denied. Also check that the agent cannot fall back to a broader credential. OAuth token exchange normally leaves the input token valid; one-time or provider-specific rules can differ. Revocation of the old and new tokens is not automatically linked. Removing broad access needs its own credential-handling and revocation plan.

Take it with you

Record what was granted and test one allowed and one forbidden operation in a safe environment. If the service cannot express the needed boundary, use an enforcing gateway or withhold that access.

Sources and evidence (2)

What we checked

Provides context

The talk recommends placing policy at the tool boundary and starting scope design with the resource server’s existing permissions.

Selected transcript passages and chapter text read on 2026-10-04. This is vendor architecture guidance, not proof that every API supports the proposed scopes.

It's 10pm. Do You Know Where Your Agents Are? · Transcript 4:52–7:23 and 21:32–22:26; chapter Start scope design with the resource

Supports

RFC 8693 distinguishes requested target resources and scope from the issued token response, whose scope must be reported if it differs.

Selected specification sections read on 2026-10-04. Provider support and enforcement must be checked separately; no token was created, exchanged or tested.

RFC 8693: OAuth 2.0 Token Exchange · Sections 2.1.1 and 2.2.1, scope and expires_in

Limits

Token exchange normally leaves the input token valid unless token-specific semantics say otherwise; linked revocation is not a general protocol property.

This limits the idea that exchange alone removes broad authority. Keeping the original credential inaccessible and testing denial are editorial deployment checks.

RFC 8693: OAuth 2.0 Token Exchange · Section 2.1, final paragraphs before 2.1.1

Editorial sources (2)

Editorial version 1.0.0 · Evidence checked 2026-10-04

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingCheck the authority a scoped token actually grants

Original edition evidence and sources

These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.

Supports

Broad long-lived credentials can be exchanged at runtime for tool-specific, task-scoped credentials so an agent receives only the authority needed for the current action.

Token exchange does not replace authorization policy, approval or audit. The credential issuer and downstream service must actually enforce the requested scope.

It's 10pm. Do You Know Where Your Agents Are? · 4:52-21:32, enforcement point, token exchange, task-scoped credentials and resource-first scope design

All sources (1)
Original edition, downloads and provenance

The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.

Version 0.1.0

No review details are supplied for this edition.

Read the original edition and overlay as JSON · Release details