escrow_submit_delivery
Hands off finished work against an escrow, as the seller. Submit the hash of the artifact plus a pointer to where it lives. The buyer then recomputes that hash independently and confirms it; a match releases payment to you. Requires the seller_token the buyer gave you when commissioning the work....
This record as markdown: /tools/com-focxle-afos/escrow-submit-delivery.md
What escrow_submit_delivery does on AFOS — Agentic Financial OS
AI agents use escrow_submit_delivery to commit financial operations through AFOS — Agentic Financial OS, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
escrow_id | string | Yes | The escrow this delivery is for. |
seller_token | string | Yes | The seller_token handed to you by the buyer. |
delivery_hash | string | Yes | Hash of the finished artifact. The buyer must be able to compute the same value from what you deliver. |
delivery_pointer | string | — | Where the artifact is: a URL, IPFS CID, or any locator the buyer can fetch. |
Parameters from the server's own tool schema.
Why escrow_submit_delivery is rated Critical
Submitting delivery triggers escrow payment release, directly moving financial funds.
From the tool's definition releases payment to you, escrow, submit delivery, seller_token
Attacks that exploit this kind of access
The rule that runs escrow_submit_delivery safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AFOS — Agentic Financial OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For escrow_submit_delivery, this is the rule to start with:
Any call to escrow_submit_delivery is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AFOS — Agentic Financial OS, apply this rule, and every escrow_submit_delivery call is checked against it from then on.
Questions about escrow_submit_delivery
Hands off finished work against an escrow, as the seller. Submit the hash of the artifact plus a pointer to where it lives. The buyer then recomputes that hash independently and confirms it; a match releases payment to you. Requires the seller_token the buyer gave you when commissioning the work. Do not start work without one. It is categorised as a Financial tool in the AFOS — Agentic Financial OS MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
escrow_submit_delivery accepts 4 parameters: escrow_id, seller_token, delivery_hash, delivery_pointer. Required: escrow_id, seller_token, delivery_hash. The full parameter table on this page comes from the server's own tool schema.
Register the AFOS — Agentic Financial OS MCP server in PolicyLayer and add a rule for escrow_submit_delivery: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches AFOS — Agentic Financial OS. Nothing to install.
escrow_submit_delivery is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the escrow_submit_delivery rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for escrow_submit_delivery. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
escrow_submit_delivery is provided by the AFOS — Agentic Financial OS MCP server (https://focxle.com/api/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AFOS — Agentic Financial OS, and thousands of servers like it.
Across the catalogue