Principle

Run agent actions in the user's authorization context

A helpful assistant should not quietly become a shared administrator.

About 1 min read

Before you use it

Use when
  • An AI acts on behalf of different users against shared downstream systems.

Keep this limit in mind

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

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

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.

An 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 your result

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

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 readingRun agent actions in the user's authorization context

Evidence and sources
Supports

OWASP recommends executing agent extensions in the specific user's authorization context with the minimum necessary scope.

User-context execution still requires server-side authorization and does not make every requested action legitimate.

LLM06:2025 Excessive Agency · Execute extensions in user's context

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details