Anonyflow for AI agents
AnonyFlow anonymizes and de-anonymizes sensitive data using encryption, helping teams meet GDPR, CCPA, and HIPAA requirements while still being able to share or process the underlying data later. 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 Anonyflow.
Anonymize sensitive data before sharing
Mask a value or a full data packet so it can be shared without exposing personal details.
Reverse anonymization when authorized
Deanonymize a previously masked value when the original data is needed for a specific task.
Confirm before deanonymizing data
Reversing anonymization exposes protected data, so it should require approval before it happens.
5 Anonyflow actions, graded by risk.
Every Anonyflow action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- anonyflow.test_connectionTest Connection
write
4Create and change things. Allow, or ask the user first.
- anonyflow.anonymize_valueAnonymize Value
- anonyflow.anonymize_packetAnonymize Packet
- anonyflow.deanonymize_valueDeanonymize Value
- anonyflow.deanonymize_packetDeanonymize Packet
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Anonyflow in three steps.
- 01Your users connect AnonyflowThey add their Anonyflow api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “anonymize Value” can wait for the user to approve.
- 03Any agent can actYour agent calls Anonyflow through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('anonyflow', { read: 'allow', write: 'ask', // anonymize_value destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Anonyflow connects.
Users add their Anonyflow 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 Anonyflow 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 Anonyflow from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore security and identity apps.
Anonyflow and Arc0, answered.
Can I use Anonyflow with Claude, ChatGPT or Cursor?
Yes. Connect Anonyflow 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 Anonyflow actions you allow.
How do users connect Anonyflow?
Users add their Anonyflow 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 Anonyflow actions can my agent take?
5 in total: 1 read, 4 write and 0 destructive, such as “anonymize Value”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Anonyflow?
Yes. Allow read actions and deny writes in the Anonyflow policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Anonyflow too?
Yes. The same Anonyflow connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Anonyflow into your agent.
Your users connect Anonyflow 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