New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

escrow_confirm_delivery

Confirms a delivery and releases payment, as the buyer. Fetch the artifact, compute its hash yourself, and report what you got. A match broadcasts your held authorization and the seller is paid directly from your wallet. A mismatch marks the escrow disputed and pays nobody. Be aware that confirmi...

SERVERAFOS — Agentic Financial OS SOURCEhttps://focxle.com/api/v1/mcp
Critical RISK CLASS
Category Financial
Parameters 33 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-focxle-afos/escrow-confirm-delivery.md

What escrow_confirm_delivery does on AFOS — Agentic Financial OS

AI agents use escrow_confirm_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.

ParameterTypeRequiredDescription
escrow_id string Yes The escrow to confirm.
buyer_token string Yes The buyer_token returned when you opened the escrow.
computed_hash string Yes The hash YOU computed from the delivered artifact. Do not copy the seller's value: recomputing it is the verification.

Parameters from the server's own tool schema.

Why escrow_confirm_delivery is rated Critical

Confirming delivery irreversibly releases funds from the buyer's wallet to the seller.

From the tool's definition releases payment...seller is paid directly from your wallet

Questions about escrow_confirm_delivery

What does the escrow_confirm_delivery tool do? +

Confirms a delivery and releases payment, as the buyer. Fetch the artifact, compute its hash yourself, and report what you got. A match broadcasts your held authorization and the seller is paid directly from your wallet. A mismatch marks the escrow disputed and pays nobody. Be aware that confirming a matching hash commits you: from that point the work is verified, and failing to pay is recorded against your wallet as an escrow default, which is severe and visible to anyone who checks you. Requires buyer_token. 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.

What parameters does escrow_confirm_delivery accept? +

escrow_confirm_delivery accepts 3 parameters: escrow_id, buyer_token, computed_hash. Required: escrow_id, buyer_token, computed_hash. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on escrow_confirm_delivery? +

Register the AFOS — Agentic Financial OS MCP server in PolicyLayer and add a rule for escrow_confirm_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.

What risk level is escrow_confirm_delivery? +

escrow_confirm_delivery is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit escrow_confirm_delivery? +

Yes. Add a rate_limit block to the escrow_confirm_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.

How do I block escrow_confirm_delivery completely? +

Set action: deny in the PolicyLayer policy for escrow_confirm_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.

What MCP server provides escrow_confirm_delivery? +

escrow_confirm_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of AFOS — Agentic Financial OS's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.