Give an agent an access token and it spreads: into the context window, into tool call logs, into notes it keeps between steps. Your agent names the user, WorkOS attaches that token, refreshes it, and releases it only to allowlisted hosts.
![[Sponsor] WorkOS: How to Give an Agent a Task Instead of a Token](/api/proxy/image?url=https%3A%2F%2Fimages.workoscdn.com%2Fimages%2F3b6999a3-68af-47d4-a9c3-04572333ddc4.png%3Fauto%3Dformat%26fit%3Dclip%26q%3D80)
Give an agent an access token and it spreads: into the context window, into tool call logs, into notes it keeps between steps.
Your agent names the user, WorkOS attaches that token, refreshes it, and releases it only to allowlisted hosts.
A hijacked agent session is a live process you can kill.
The page is ready to read now. The fuller skim-friendly version will appear here automatically.
Give an agent an access token and it spreads: into the context window, into tool call logs, into notes it keeps between steps. Your agent names the user, WorkOS attaches that token, refreshes it, and releases it only to allowlisted hosts. A hijacked agent session is a live process you can kill.
A hijacked agent session is a live process you can kill.
Open the app view to save this story, compare related coverage, and continue from the same source.