[FIAT ESCROW] Release escrowed funds to seller. Triggers on-chain escrow release + SPEI/wire payout. PRE-CONDITIONS (ALL must be met for live payments): 1. Payment status must be 'in_custody' or 'ready_for_release' 2. Seller KYC must be 'approved' (seller must complete identity verification) 3. F...
Part of the Kustodia Escrow server.
Free to start. No card required.
AI agents call release_funds to retrieve information from Kustodia Escrow without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though release_funds only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"release_funds": {}
}
}See the full Kustodia Escrow policy for all 36 tools.
These attack patterns abuse exactly the kind of access release_funds gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
[FIAT ESCROW] Release escrowed funds to seller. Triggers on-chain escrow release + SPEI/wire payout. PRE-CONDITIONS (ALL must be met for live payments): 1. Payment status must be 'in_custody' or 'ready_for_release' 2. Seller KYC must be 'approved' (seller must complete identity verification) 3. For MXN payouts: seller must have a beneficiary_clabe (18-digit CLABE) - check via check_status 4. For USD payouts: seller must have an external_account_id (US bank via Bitso) 5. For standard payments: buyer payer_approval must be true (unless vehicle_verification or ready_for_release) If any pre-condition fails, use check_status to see what's missing, then guide the user to complete the requirement before retrying. FLOW AFTER RELEASE: 1. On-chain escrow released (tokens return to bridge wallet) 2. Tokens transferred to Juno (MXNB) or Bitso (USDC) 3. Fiat payout initiated (SPEI to seller CLABE or USD wire) 4. Payment status → 'released' → 'completed'. It is categorised as a Read tool in the Kustodia Escrow MCP Server, which means it retrieves data without modifying state.
Register the Kustodia Escrow MCP server in PolicyLayer and add a rule for release_funds: 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 Kustodia Escrow. Nothing to install.
release_funds is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the release_funds 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 release_funds. 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.
release_funds is provided by the Kustodia Escrow MCP server (kustodia/escrow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Kustodia Escrow tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.