Acting on Behalf of a Supervisor
Some tools belong to a person, such as a Jira project, a mailbox or a Copilot conversation. When an agent needs one, HYPR AgentPass™ lets it act on behalf of its supervisor.
The supervisor authorizes once. The gateway then holds a scoped token and attaches it to the agent's calls. The agent never sees a credential, and the token reaches only what the supervisor authorized.
Where It Applies
Delegation works on four surfaces, each authorized differently.
| Surface | How the supervisor authorizes | Where you see it |
|---|---|---|
| MCP connectors protected by OAuth | Once, from their agent, when the tool first asks. The gateway completes the handshake and refreshes the token | The connector's Connections tab lists each supervisor's authorization, and Reset token clears one. See MCP Servers |
| Microsoft 365 Copilot | By signing in to the Agent Portal. Copilot answers with that person's permissions | Connecting Microsoft 365 Copilot |
| AWS Bedrock AgentCore agents | Per user, when Per-user isolation is on, so each person's tool credentials stay separate | AWS Bedrock AgentCore Agents |
| Service agents | The owner opts the service agent in to act as them on named connectors | Creating a Service Agent |
In every case, the tool call is recorded against both the agent and the supervisor. The supervisor's role still bounds which tools the agent is offered. See Controlling MCP Tool Access by Role.
Related
- Agent Identity — the identity the agent carries itself
- Supervisor Identity — the person whose scope is delegated
- Identity and Token Model — the three identities on one request