Skip to main content
Version: 11.5.0

Policies and Guardrails

HYPR AgentPass™ decides what every agent may do at the gateway, as each request passes. This section covers each control, what it decides, and who can set it.

The Controls​

ControlWhat it decidesWho sets it, out of the boxStart with
IdentityWhich agent sent a request, and which person is accountable for itAdmin and Operator import agents and turn them off and on. A supervisor approves their own agents' onboardingIdentity
PoliciesWhether a request is allowed, blocked or held for approvalAdmin, and Operator and Supervisor for their own policies. Every role except Model governance owner can read themPolicies
Tool accessWhich MCP tools an agent may see and call, by its supervisor's rolesAdminControlling MCP Tool Access by Role
Data classificationHow sensitive the data each tool and connector handles isAdminData Classification
Session trackingWhat a session has already read, carried forward to its later callsAdminSession Tracking
GuardrailsHolding or stopping a call that looks like indirect prompt injection, alerting on it, and containing the agentAdmin and Security analyst work alerts. Admin saves settingsGuardrails
Session controlFreezing one live session, and resuming or ending itAdmin and Security analyst, and the session investigatorPausing and Stopping a Session
Session investigatorWhether a flagged coding-agent session should continue, pause or terminateAdminThe Session Investigator

Each page names the permission a task needs. Permissions by Role lists every role's permissions by area.

Tools Governance​

AgentPass governs tools on four axes. Each axis answers a different question, and has its own page.

AxisQuestion it answersWhere it is set
Role-based access (RBAC)Which tools may an agent call? The tools follow the supervisor's roles, both in the list an agent sees and at call timeControlling MCP Tool Access by Role
ScopeWhich connectors does this rule or credential reach? A policy is scoped to connectors, and a workload agent carries a named set of connectors it may useHow Policies Are Evaluated · Workload Agents
LineageWhich thread of which session made this call? Sessions group a conversation's requests, subagent attribution splits them, and an evaluator can review themSubagent Attribution · Session Watch
ClassificationWhat does this tool handle? A tier and tags on each tool and connector let a policy target the sensitivity of the data, not the name of the toolData Classification

Session tracking extends classification across calls. It carries what a session has already read forward to its later calls. See Session Tracking.