The Four Controls
Every request an agent sends through HYPR AgentPass™ passes four controls in the gateway. Each control has one home in this section.
| Control | What it does | Configure it in |
|---|---|---|
| Identity | Makes every agent attributable: to the agent's own credential, to the supervisor behind it, or to a scoped grant made on a supervisor's behalf | Identity |
| Policy | Allows a request, blocks it, or asks a person. A rule is evaluated on each request and, where you choose, on each response | Policy |
| Record | Keeps the Request Log, sessions and discovered agents, and decides how long any of it is kept | Activity Dashboard · Agent Session Forensics · Data Management |
| Tools governance | Decides which tools a role may call, which connectors a rule or a service agent may reach, and which thread of a session did the work | Tools Governance |
The gateway applies these controls to whatever it forwards traffic to. A connector holds the configuration for one provider or tool: an AI provider, an MCP server, a REST API, a cloud agent or a chat channel. See Connectors.
Related
- How It Works — where the gateway sits between agents, guards and providers
- Architecture: The Request Path — the same picture in full