ABOUT THIS EPISODE
John Gren wanted an agent to read Jira, compare product requirements against existing tickets, and find gaps in the roadmap. The API key he gave it could write. Soon colleagues were asking him on Slack why he was changing their priorities, and Jira showed every edit as his.
ㅤ
Tim Tyler and John work through why that happened and what delegation should look like instead. John came up through identity and access management, so his instincts come from the security side. Yet he sounds like the person shipping the agents when he calls limiting their autonomy “strictly counterproductive.” His fix pulls apart what the API key had fused together: the agent’s own identity, the authority John delegates to it, and a separate check on what it may do with that authority. The boundary he draws: if John can delete repositories in GitHub, an agent acting for him shouldn’t automatically be able to.
ㅤ
👤 Guest Bio
John Gren is Director of Product Management at Gravitee, where he has worked on product vision and strategy since 2022, moving from API management into event stream management and AI agent management. His recent focus is LLMs, MCP, agent-to-agent communication, and identity, access, and authorization for agents. Before Gravitee he held integration, identity and access management, and architecture roles. He gave a keynote on agent experience at the Nordic APIs Platform Summit 2025.
ㅤ
📌 What We Cover
- The point where AI turns into an accountability problem: when agents get enterprise data and tools and start acting on someone’s behalf
- Why John calls cost “an effect of something” and puts agent identity and visibility first, wherever the agent was built
- The Jira agent asked to read the roadmap that started reprioritizing tickets, and why nothing in the record could separate its edits from John’s
- Impersonation vs. delegation: why a static API key is worse than a handed-over OAuth token, and how OAuth Token Exchange (RFC 8693) produces a token naming both the user and the agent
- Who’s responsible when an agent acts: the user who delegated, plus an internal sponsor who can revoke the agent’s access
- How authorization has “always fallen between the cracks” in identity and access management, and a policy that lets John write a Jira ticket while refusing the same write to the agent acting for him
- Guardian agents for decisions too dynamic for a written rule, such as a support refund that needs a finance manager’s approval
- Logging every authorization decision with the policy version that made it
ㅤ
🔗 Resources Mentioned
- Model Context Protocol (MCP), including its authorization specification
- OAuth 2.0 Token Exchange, RFC 8693
- OAuth Client ID Metadata Document
- SPIFFE
- OpenID Foundation AuthZEN Authorization API
- Microsoft Purview
- Jira
ㅤ
Trusted2Act is presented by Gravitee.