Leave the bearer out of task descriptions. Naming the subject is fine. Interpolating authdog_token into a task puts the bearer in the prompt, which this hook is written to prevent.
What the model can see
The model can see the subject the hook already verified, and a refusal when the hook stopped the call. It cannot see the access token or the client secret. A prompt that asks the model who the caller is ignores the hook. The hook already returned unauthorized when userinfo did not accept the bearer.
Do not copy the token into graph state, crew inputs that tasks render, callback state the model reads, or telemetry context.
Related
| Read | To learn how to |
|---|---|
| Authorizing tool calls for CrewAI | Refuse work after the subject is known |
| Custom channel auth for CrewAI | Keep the bearer on the hook |
| CrewAI | See the planned sample |
| API keys and M2M for CrewAI | Keep the secret on the caller |