The bearer helper is configured for third-party API hosts, but the relevant risk is the broader broker flow: grant material and a recoverable token reach Catarina, and the included server-side code decrypts the third-party secret. The behavior is disclosed and user-triggered, but the Credentials rule treats another service's credential reaching the publisher's service as a block.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs `csec connect` or an agent invokes MCP `call_api` and a grant is created.
Mechanism
The client sends encrypted secret material and a key hash to the Catarina service, then forwards the grant token with broker requests. The included server-side grant code can use that token to decrypt the secret.
Attack narrative
When a user runs `csec connect` or an agent creates a broker grant, the client encrypts a third-party secret and registers the grant with Catarina. The child receives a grant token, which the local proxy forwards to Catarina with API requests. The package includes server-side code that uses the token to decrypt the secret; the broker is intended to attach it to requests sent to the selected third-party host. This exposes the other service's credential to the publisher's service as part of the product's normal broker flow.