Workflow
Agents, Access, and the Future of Machine Identity — Nick Nisi (WorkOS) + Lizzie Siegle (Cloudflare)

Agent & MCP Server Development - Cloudflare and Work OS are collaborating to promote the idea that agents acting on behalf of users need the same credentials and authorization as user-facing projects [1] - The industry is moving towards more fine-grained authorization for AI agents, potentially authorizing per-line changes, per-tool changes, or even network connections [20] - Cloudflare offers a free tier for Durable Objects, which can be used for persistent storage in agents [3] Cloudflare's Offerings - Cloudflare provides compute cloud workers, AI model hosting, vectorized inference, vector database, SQL database, durable objects, video streaming, and image optimization [2] - Cloudflare workers have bindings that allow interaction with other Cloudflare products and other companies' products [3] - Cloudflare's agents framework includes an OAuth framework for setting up authorization, enabling easy identification of the worker or agent acting on behalf of a user [5] MCP Server Demo & Use Case - A basic MCP server was built using Cloudflare and Work OS, which is available for users to check out and run [6] - The demo showcases ordering a shirt via an agent, demonstrating how agents can act on behalf of users with proper authorization [9][10][11] - The demo uses Cloudflare's key-value storage to save order data, accessible through the interface [12] - Durable Objects can store data directly on the context associated with a worker object, unique for each user [14][16] Security & Authorization - The industry emphasizes the importance of audit trails with OAuth tools to track agent interactions, including reasons for interaction, the user on whose behalf it acted, and the outcome [21] - The industry needs to consider users as deputies who have access to tools and can potentially misuse them [21]