Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: 11.3.0

HYPR AgentPass: How It Works

HYPR AgentPass™ sits between the agents your people run and the providers and tools those agents call. Every request is attributed to an agent, judged by your policies and recorded. Where you require it, a person approves it first.

Agents on the left reach the gateway through a guard or the Agent Portal. The gateway applies Identity, Policy, Record and Tools governance, then forwards to LLM providers, MCP servers or REST APIs. Where policy requires it, a supervisor approves or denies from the HYPR mobile app.

Agents​

Agents reach the gateway from a workstation or from a managed cloud platform:

  • Local coding agents: Claude Code, Codex CLI and Cursor
  • Provider-managed agents: Anthropic cloud agents, AWS Bedrock AgentCore and Microsoft 365 Copilot

Each agent carries an identity the gateway can attribute. See Agents.

Guards and the Agent Portal​

Endpoint Guard reports supported workstation activity and applies managed controls on macOS and Windows. The Agent Portal brings conversations with provider-managed agents through the gateway. See Enforcement Points.

Gateway​

Four controls act on every request:

  • Identity makes every agent attributable.
  • Policy allows a request, blocks it, or asks a person.
  • Record writes the Request Log and applies retention.
  • Tools governance decides which tools a role may reach, with scope and lineage.

Connectors describe the providers and tools the gateway reaches. See Gateway.

Identity​

Three identities are in play on a request:

  • The agent's own token, assigned by AgentPass
  • The supervisor's identity, which the agent uses directly for tools that person is entitled to
  • A scoped on-behalf-of session token, for actions the supervisor delegates

See Identity.

Supervision​

When a policy asks for a person, the gateway holds the request and notifies the supervisor on the HYPR mobile app. The supervisor chooses Approve or Deny with a passkey. The decision is signed and recorded.

Agents and supervisors can also exchange messages over a chat channel, and agents can send one-way notifications. See the Supervisor Guide.

Providers and Tools​

Approved traffic goes on to LLM providers, MCP servers, REST APIs and managed cloud agents. See Connectors.