Remote Retrieval for AI agents
Remote Retrieval coordinates equipment retrieval logistics, letting IT teams create and track return orders for laptops and monitors from remote employees. 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 Remote Retrieval.
Check pending returns
List pending orders to see which employees still have equipment to send back.
Look up device pricing
Get device prices before deciding how to handle a lost or damaged laptop.
Confirm before creating an order
Get the order details and company account first, then create a new retrieval order only after review.
7 Remote Retrieval actions, graded by risk.
Every Remote Retrieval action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- remote_retrieval.get_all_ordersGet All Orders
- remote_retrieval.get_device_pricesGet Device Prices
- remote_retrieval.get_order_detailsGet Order Details
- remote_retrieval.get_company_detailsGet Company Details
- remote_retrieval.list_pending_ordersList Pending Orders
- remote_retrieval.validate_userRemoteRetrieval: Validate User
write
1Create and change things. Allow, or ask the user first.
- remote_retrieval.create_orderCreate Order
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Remote Retrieval in three steps.
- 01Your users connect Remote RetrievalThey add their Remote Retrieval api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Order” can wait for the user to approve.
- 03Any agent can actYour agent calls Remote Retrieval through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('remote_retrieval', { read: 'allow', write: 'ask', // create_order destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Remote Retrieval connects.
Users add their Remote Retrieval 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 Remote Retrieval 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 Remote Retrieval from any agent.
Remote Retrieval and Arc0, answered.
Can I use Remote Retrieval with Claude, ChatGPT or Cursor?
Yes. Connect Remote Retrieval 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 Remote Retrieval actions you allow.
How do users connect Remote Retrieval?
Users add their Remote Retrieval 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 Remote Retrieval actions can my agent take?
7 in total: 6 read, 1 write and 0 destructive, such as “create Order”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Remote Retrieval?
Yes. Allow read actions and deny writes in the Remote Retrieval policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Remote Retrieval too?
Yes. The same Remote Retrieval connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Remote Retrieval into your agent.
Your users connect Remote Retrieval once, under your brand. Your agent gets 7 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan