Skip to main content
Version: 11.5.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 and a person, checked against your policies and recorded. Where a policy asks for a person, a supervisor decides before the request goes on.

Agents reach the AgentPass gateway through Endpoint Guard or the Agent Portal. The gateway applies Identity, Policy, Record and Tools governance, and forwards requests to AI providers, MCP servers, REST APIs and cloud agents. When a policy asks for a person, the request is held until a supervisor approves or denies it on the HYPR mobile app or the console.

Agents​

An agent is software that uses a model and tools to complete a task. AgentPass governs agents wherever they run:

  • Local agents run on a person's workstation, such as Claude Code, Codex CLI and Cursor.
  • Cloud agents are hosted by a provider, such as Anthropic, AWS Bedrock AgentCore and Microsoft 365 Copilot.
  • Workload agents run on their own, with a named owner and a role and credential of their own.

Every agent appears on the console's Agents page. See Where Agents Run.

Guards and the Agent Portal​

Two enforcement points bring agent traffic to the gateway.

Enforcement pointWhere it runsWhat it does
Endpoint GuardmacOS and Windows workstationsReports AI tool activity, routes supported tools to the gateway, provisions MCP servers and blocks direct traffic to providers
Agent PortalThe gateway, in a browserCarries people's conversations with provider-hosted cloud agents, and applies the same controls to them

See Endpoint Guard and Agent Portal.

Gateway​

The gateway applies four controls to the traffic it carries.

ControlWhat it doesConfigure it in
IdentityAttributes every request to an agent, and to the person accountable for itIdentity
PolicyAllows a request, blocks it, or holds it for a person. A rule can check the request and, where you choose, the responsePolicies
RecordWrites every request to the Request log, groups requests into sessions, and keeps them for as long as your retention settings allowRequest Log · Data Management
Tools governanceDecides which tools each role may see and call, which connectors an agent may reach, and how sensitive the data a tool handles isTools Governance

Guardrails build on these controls. They track what a session has read, hold a risky action after the session reads untrusted content, and can pause a live session. The console marks Guardrails as Preview. See Input Guardrails.

Architecture: The Request Path follows one request through these controls in order.

Identity​

A request carries one of three identities:

  • The agent's own credential, which AgentPass issues and ties to an accountable owner
  • The supervisor's identity, used directly by an agent working for that person, such as a coding agent on their workstation
  • A scoped session token, which the gateway issues when a supervisor lets an agent use a tool on their behalf. The gateway keeps the tool's credential, and the agent never holds it

See Identity and Token Model.

Supervision​

When a policy requires approval, the gateway holds the request and asks the agent's supervisor. The supervisor chooses Approve or Deny on the HYPR mobile app, or on the console's Approvals page. A request nobody answers expires, and an expired request never counts as an approval.

With Require signed approvals set to Required (production), every approval must carry the supervisor's passkey signature, so the record shows the decision was theirs. Under Optional (soak), an approval can be recorded without a signature. A denial needs no passkey under either setting.

Agents and supervisors can also exchange messages on a two-way chat channel, and an agent can send one-way notifications to its supervisor. See Being a Supervisor.

Providers and Tools​

Traffic the gateway allows goes on to the systems your connectors describe:

  • AI providers, such as Anthropic, OpenAI, AWS Bedrock and Microsoft Foundry
  • MCP servers and REST APIs
  • Cloud-agent platforms

Where the gateway holds a tool's credential, it attaches it as it forwards the call, so the agent never sees it. A channel connector, such as Slack, works the other way: it brings people's messages in to a cloud agent. See Connectors.