# Exchange broad credentials for task-scoped access

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Exchange broad credentials for task-scoped access

ID: MHC-D-RESEARCH-1173 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/exchange-broad-credentials-for-task-scoped-access

Do not hand an agent the master key when it needs one door for one job.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

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

### Avoid when

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

### Explanation

At the tool boundary, exchange delegated identity for a short-lived credential scoped to the resource and action the task actually needs. Keep policy and approval outside the model, and log which authority was granted for each consequential call.

### Steps

1. Start scope design from the resource and action being requested.
2. Issue or exchange for the narrowest practical short-lived credential.
3. Enforce scope in the downstream service, not in prompt text.
4. Require approval for authority the current task should not receive automatically.
5. Log the granted scope with the action.

### Example

An incident agent may read the current ticket and restart one service, but it does not inherit a broad cloud administrator key for the entire account.

### Check

A mistaken model action outside the task's granted scope is rejected even if the prompt asks for it.

### Limits

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

### Evidence and sources

- 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. — RS-3834F341D660F727. Token exchange does not replace authorization policy, approval or audit. The credential issuer and downstream service must actually enforce the requested scope. (4:52-21:32, enforcement point, token exchange, task-scoped credentials and resource-first scope design)
- RS-3834F341D660F727: It's 10pm. Do You Know Where Your Agents Are? — https://ai.engineer/talks/I3znWC3MEXM-its-10pm-do-you-know-where

### Vedokrok editorial review

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.

#### 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.

**Editorial takeaway:** 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.

#### Editorial evidence

- contextualizes: The talk recommends placing policy at the tool boundary and starting scope design with the resource server’s existing permissions. — RS-3834F341D660F727. 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. (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. — oauth-token-exchange. Selected specification sections read on 2026-10-04. Provider support and enforcement must be checked separately; no token was created, exchanged or tested. (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. — oauth-token-exchange. This limits the idea that exchange alone removes broad authority. Keeping the original credential inaccessible and testing denial are editorial deployment checks. (Section 2.1, final paragraphs before 2.1.1)
- RS-3834F341D660F727: It's 10pm. Do You Know Where Your Agents Are? — https://ai.engineer/talks/I3znWC3MEXM-its-10pm-do-you-know-where
- oauth-token-exchange: RFC 8693: OAuth 2.0 Token Exchange — https://www.rfc-editor.org/rfc/rfc8693.html

Editorial version: 1.0.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/run-agent-actions-in-the-user-s-authorization-context
