# Run agent actions in the user's authorization context

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

---

## Run agent actions in the user's authorization context

ID: MHC-D-RESEARCH-0311 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/run-agent-actions-in-the-user-s-authorization-context

A helpful assistant should not quietly become a shared administrator.

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

### Use when

- An AI acts on behalf of different users against shared downstream systems.

### Avoid when

- User-context execution does not make malicious or mistaken user requests safe; policy and high-impact approval may still apply.

### Explanation

Carry the initiating user's identity and allowed scope into downstream calls instead of using one generic high-privilege service identity for everyone. Let the destination system enforce what that user can access. This keeps the agent from turning a reasoning mistake into cross-user authority.

### Example

A repository assistant uses the user's OAuth scope for the selected repository rather than a token that can edit every repository in the organization.

### Check

Changing the user changes the resources and actions the downstream system authorizes.

### Limits

- User-context execution does not make malicious or mistaken user requests safe; policy and high-impact approval may still apply.

### Evidence and sources

- supports: OWASP recommends executing agent extensions in the specific user's authorization context with the minimum necessary scope. — RS-EEEBBCF69A614717. User-context execution still requires server-side authorization and does not make every requested action legitimate. (Execute extensions in user's context)
- RS-EEEBBCF69A614717: LLM06:2025 Excessive Agency — https://genai.owasp.org/llmrisk/llm062025-excessive-agency/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/enforce-permissions-outside-the-model
