EnforcedFlow for AI agents
EnforcedFlow routes incoming work across teams using round-robin groups, agent availability, and configurable assignment criteria, used by support and sales operations balancing workload fairly. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in EnforcedFlow.
Assign the next available agent
Select the next agent in a round-robin group to route a new lead or ticket to.
Check a group's routing rules
Get a group's routing fields to confirm how assignments are being decided.
Read-only agent roster checks
List the agents in a round-robin group as a read-only step before adjusting assignment order.
5 EnforcedFlow actions, graded by risk.
Every EnforcedFlow action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- enforcedflow.list_groupsList Round Robin Groups
- enforcedflow.get_group_fieldsGet Group Routing Fields
- enforcedflow.list_group_agentsList Group Agents
write
2Create and change things. Allow, or ask the user first.
- enforcedflow.select_next_agentSelect Next Agent
- enforcedflow.upsert_group_agentUpsert Group Agent
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
EnforcedFlow in three steps.
- 01Your users connect EnforcedFlowThey add their EnforcedFlow api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “select Next Agent” can wait for the user to approve.
- 03Any agent can actYour agent calls EnforcedFlow through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('enforcedflow', { read: 'allow', write: 'ask', // select_next_agent destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How EnforcedFlow connects.
Users add their EnforcedFlow api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same EnforcedFlow connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use EnforcedFlow from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
EnforcedFlow and Arc0, answered.
Can I use EnforcedFlow with Claude, ChatGPT or Cursor?
Yes. Connect EnforcedFlow to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the EnforcedFlow actions you allow.
How do users connect EnforcedFlow?
Users add their EnforcedFlow api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which EnforcedFlow actions can my agent take?
5 in total: 3 read, 2 write and 0 destructive, such as “select Next Agent”. Your policies decide which of them each agent may call.
Can I make my agent read-only in EnforcedFlow?
Yes. Allow read actions and deny writes in the EnforcedFlow policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call EnforcedFlow too?
Yes. The same EnforcedFlow connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug EnforcedFlow into your agent.
Your users connect EnforcedFlow once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan