How BlueBear handles the work
Do not treat the agent name as identity
Resolve the authenticated actor, tenant, workspace, agent definition and workflow version independently. A prompt claim or display name is not an authorization credential.
Evidence: Authenticated subject plus tenant, workspace, agent, and workflow identifiers
Authorize capabilities, not broad access
Evaluate the MCP connection, tool, action class, resource, scope, budget, and approval requirement for each consequential action.
Evidence: Requested capability, effective policy, allow or deny result, and reason
Keep credentials at the execution boundary
Resolve the approved connector credential only after policy permits the action. Return the scoped result rather than exposing a reusable bearer token to model context.
Evidence: Credential reference, audience, expiry, execution receipt, and redaction state
Preserve delegation and human decisions
Retain who delegated work, which authority the agent exercised, where approval changed the plan, and which downstream outcome was accepted.
Evidence: Delegation chain, approval event, tool receipt, and outcome correlation