Session brief
Agents, Access, and the Future of Machine Identity — Nick Nisi (WorkOS) + Lizzie Siegle (Cloudflare)
Overview
This talk explores the evolving landscape of AI agents, emphasizing the critical need for robust authorization and identity management as these agents act on behalf of users. It highlights how existing human-centric authorization frameworks, like OAuth, are becoming essential for AI agents to securely interact with tools and services. The discussion also touches upon the infrastructure required to support these agents, including persistent storage and edge computing capabilities.
Who should watch
- AI engineers and builders developing agentic workflows.
- Product Managers and engineers focused on shipping AI-powered features.
- Developers seeking to understand how to secure and manage agent access to tools.
- Anyone interested in the practical application of AI agents in automating tasks.
Key takeaways
- AI agents require sophisticated authorization mechanisms, similar to those used for human users, to control their actions and access to tools.
- Frameworks like OAuth are no longer solely for human authentication but are crucial for managing agent identity and permissions.
- Cloudflare's infrastructure, including Durable Objects for persistent memory and Workers for edge compute, provides a strong foundation for building and deploying AI agents.
- Integrating agents with existing tools and services can be streamlined by treating agents as programmatic users with defined credentials.
- The development of agentic systems necessitates careful consideration of security, audit trails, and the potential for misuse of granted access.
- A practical demonstration showcased an agent ordering a shirt using tools integrated via an MCP server, highlighting the end-to-end workflow.
- Persistent storage, such as Cloudflare's KV or Durable Objects, is vital for agents to maintain state and user-specific information.
- The future of agent authorization points towards more granular control, potentially down to per-line code changes or specific tool invocations.
Notable quotes
The point is that oath really just isn't for humans anymore. It's for our agents acting on our behalf.
Think of your users not as users but as deputies they have access to tools and they can use and also misuse them as well.
Unofficial community note. Prefer the recording for nuance.