Requiring a HYPR Identity on an MCP Connector
Overview
An MCP server connector set to OAuth authentication expects each caller to hold its own credential for the server behind it. The caller authorizes to that server directly. HYPR AgentPass™ forwards the request with the caller's credential attached. This pass-through arrangement is the default.
With pass-through, the gateway forwards the request without knowing who the caller is. The Inbound authentication setting changes that. If you require a HYPR identity, only a caller the gateway recognizes reaches the server: a person signed in through the gateway, or a service agent.
Editing a connector is an administrator task, and needs permission to view and edit connectors.
When to Require an Identity
Requiring an identity makes the rest of your controls apply to a connector's traffic. Once the gateway knows who is calling, it can attribute the call in the Request Log. It can also govern the call by the caller's role, and match it in a policy that names an agent.
Turn it on when:
- You want every call to this server attributed to a known caller, not an anonymous client.
- You want the connector's tools governed by role, so the tool grants on a role decide what a caller reaches here.
- You want policies that match on the calling agent to apply to this connector.
Leave it as pass-through when the server is meant for clients that hold their own credential and that you do not manage through AgentPass.
Set Inbound Authentication
- Open Connectors.
- Edit the MCP server connector.
- Confirm Authentication is set to OAuth. The setting appears only for that method. See Where the Setting Applies.
- Set Inbound authentication to one of the options in the following table.
- Click Save. The change applies to the next request.
The two options require different callers.
| Option | What the gateway requires |
|---|---|
| Pass-through (current behaviour) | Any caller presenting a credential for the server behind the connector. This is the default |
| Require a HYPR identity | A caller the gateway recognizes: a signed-in person or a service agent. Others are refused |
Requiring an identity refuses callers the connector accepted before. Before you change it, check the connector's traffic in the Request Log to see who calls it today. Make sure each caller has a HYPR identity: a person who signs in through the gateway, or a service agent with this connector in scope.
Where the Setting Applies
Inbound authentication exists for the one case where the gateway would otherwise not need to know the caller. The other two MCP server authentication methods already require an identity on every call, so they have no setting to change.
| Authentication | Inbound requirement |
|---|---|
| OAuth | Your choice: pass-through, or require a HYPR identity |
| API Token | Always requires a HYPR identity. The gateway lends its own stored token to the call, so it will not do that for a caller it cannot name |
| OAuth (Managed by Gateway) | Always requires a HYPR identity. The gateway holds and refreshes the tokens on a person's behalf, so it needs to know whose call it is |
The setting can only tighten a connector. It is not offered for the other two methods, and AgentPass declines to save it against them. No combination relaxes a requirement.
An MCP server connector where the setting was never changed behaves as pass-through.
Related
- Service Agents — the identity a machine caller uses to satisfy this requirement
- Connecting a Service Agent — present a credential and read a refusal
- Configuring Connectors — the kinds of connector, including MCP servers
- Controlling MCP Tool Access by Role — what a known caller's role permits once identity is required
- Policies — rules that can match the calling agent