Skip to content
AI Agent Access Control

Decide for each tool whether the action runs with the agent's authority or the signed-in user's

Check 22 of 30: Decide for each tool whether the action runs with the agent's authority or the signed-in user's. If a tool runs with the agent's authority, every user can reach whatever the agent can reach. If it runs with the user's authority, the agent can only do what that user may.

The whole checklist ยท The map

Why it matters

If a tool runs with the agent's authority, every user can reach whatever the agent can reach. If it runs with the user's authority, the agent can only do what that user may.

How, in each cloud

AWS
AgentCore Gateway lets each target use the gateway role, the caller's credentials, or a token exchange that carries the user and agent identities.
Google Cloud
Google describes separate user, agent and delegated identities; delegated calls are governed by both the agent's policies and the user's permissions.
Azure
Foundry documents application-only access (agent's own authority) and delegated access (on behalf of the signed-in user, in preview).

What the documentation says

  • "for a new, scoped access token that targets a downstream resource." (source)
  • "acts on behalf of the initiating human user using scoped 3-legged OAuth" (source)
  • "Application-only access : The agent acts under its own authority, without a signed-in user." (source)
  • "Delegated access : The agent acts on behalf of the signed-in user." (source)

Sources

  1. docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-outbound-auth.html, read 10 Nov 2026
  2. docs.cloud.google.com/gemini-enterprise-agent-platform/govern/identity-delegatio, read 10 Nov 2026
  3. learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/agent-identity, read 10 Nov 2026
  4. learn.microsoft.com/en-us/azure/ai-foundry/agents/concepts/agent-identity, read 10 Nov 2026

Last reviewed 16 Nov 2026.