TL;DR: Session-scoped access is the standout finding in WorkOS’s March 31 update, which shows AI agent access moving toward bounded runtime delegation. Identity teams need tighter limits on token lifetime and approval paths as code-driven access changes spread beyond the dashboard.
Editorial analysis by NHI Mgmt Group, based on content published by WorkOS: “March Updates”.
Key questions
Q: Why do session-scoped permissions matter for AI agents?
A: Session-scoped permissions limit how far an agent can move if its behaviour changes mid-task or a tool connection is overused.
Q: What breaks when multiple apps share the same identity model?
A: Policy drift becomes more likely because web, mobile, and agent-assisted flows often need different session lifetimes and callback handling.
Q: How should teams control AI agent access to downstream tools?
A: Teams should treat agent access as a bounded runtime grant, not a generic application permission.
Practitioner guidance
- Define session-scoped delegation for agents Set explicit session limits for agent access to third-party data connections and require re-approval when scope changes during a task.
- Separate application policy boundaries Assign distinct client IDs, redirect URIs, session lifetimes, and credentials to each application so agent and user flows do not inherit one another's policy settings.
- Audit CLI-driven identity changes Require logging, review, and rollback for any configuration or resource changes made through the CLI, including agent-triggered updates.
Bottom line: AI agent access is moving toward session-based delegation, which changes the governance focus from login to bounded runtime privilege.
Glossary terms: Pipes MCP, Task-scoped Delegation, Application boundary, CLI-based identity administration
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Agent-facing identity control is becoming a runtime governance problem, not a login problem. WorkOS’s update shows the control point moving from initial authentication to what the agent can do after sign-in. That matters because agent activity now depends on session scope, application context, and delegated tool access, which are all governance decisions rather than UI details. Practitioners should read this as a shift in where identity policy must operate.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How do identity teams decide whether CLI-based automation is safe?
A: The test is whether configuration changes made through code are still subject to the same review, logging, and rollback controls as dashboard changes. If they are not, the CLI becomes a parallel administration path with weaker oversight. Safe use depends on governance parity, not on the interface used to make the change.
👉 Read our full editorial: WorkOS CLI and Pipes MCP shift identity control for AI agents