AiHummer
English▾
Sign inAccount
v1.6.x▾
{ }Swagger

Personal identity, MCP and external agents

v1.6.x · updated 2026-11-15

An external connection has two separate decisions: who you are in that service and what the current AiHummer agent may do. Signing in through an enterprise identity provider does not itself grant tool, workspace or document access.

Configure a personal connection

An administrator configures a supported external-identity profile and its exact service endpoint in Connections. The profile must match the real issuer, audience, requested scopes and supported token lifetime. The administrator explicitly maps the external subject and assigns the permitted users, groups and agents. Do not paste another person’s account identifier into an agent request.

Use your own offered sign-in path. A normal verified token renewal can preserve the same account binding; replacing an opaque manual token does not prove that it belongs to the same person. Expired, revoked or changed connections need current authorization before further content is disclosed.

Use the server’s actual MCP profile

Select the protocol profile supported by the connected MCP server. Available tools, resources and resource templates come from that server under the current account. A resource link is data, not permission to open an arbitrary address. Progress updates describe the current operation; they are not proof of its business result.

When the server requests input, review its concrete question and supported fields. Do not supply a credential to an unrelated form. External instructions and resource text do not override your approvals or the agent’s tool restrictions. Long-running supported operations use External tasks.

Delegate to an external agent

For a configured outbound A2A peer, the administrator selects the HTTPS service, public agent card and approved identity profile. This path supports the configured A2A 1.0 JSON-RPC interface; it is distinct from a separately published inbound chat endpoint. A card or remote agent name grants no local access.

Ask the assigned agent to delegate a clearly bounded request. After interruption, read the saved receipt and check the original remote task. Continue only a current request for input; request cancellation against the same task. An uncertain send must not be recreated merely because its reply is missing. Remote completion and returned artifacts still require independent review. Linked artifacts are not automatically fetched as trusted files.

Source-processing restrictions apply to delegation as well as ordinary model requests. If no compatible route or current account exists, resolve that refusal rather than switching to an unrestricted service.