[FIAT ESCROW] Create a fiat escrow payment. Returns deposit instructions (CLABE for MXN, wire for USD). HOW FUNDING WORKS (IMPORTANT): The MCP does NOT fund fiat escrows. After creation, this tool returns deposit instructions (CLABE or wire details). The BUYER must deposit funds themselves via SP...
Risk signalsHigh parameter count (19 properties)
Part of the Kustodia Escrow server.
Free to start. No card required.
AI agents use create_escrow to create or modify resources in Kustodia Escrow. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call create_escrow repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Kustodia Escrow.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"create_escrow": {
"limits": [
{
"counter": "create_escrow_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Kustodia Escrow policy for all 36 tools.
These attack patterns abuse exactly the kind of access create_escrow gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
[FIAT ESCROW] Create a fiat escrow payment. Returns deposit instructions (CLABE for MXN, wire for USD). HOW FUNDING WORKS (IMPORTANT): The MCP does NOT fund fiat escrows. After creation, this tool returns deposit instructions (CLABE or wire details). The BUYER must deposit funds themselves via SPEI or bank wire. The platform detects the deposit automatically. Your job as the agent: present the CLABE/wire instructions to the user and tell them to make the deposit. To check if the deposit arrived, use check_status. For web3 wallet-to-wallet escrows where the AGENT can fund, use create_web3_escrow + fund_web3_escrow instead. PAYMENT TYPES: - 'standard' (default): General marketplace escrow. Only requires amount, currency, payer/recipient emails. - 'vehicle_verification': Car purchase escrow. REQUIRES: vehicle_vin, vehicle_make, vehicle_model. Also accepts: vehicle_year, vehicle_plate, vehicle_color, vehicle_mileage. - 'mechanical_inspection': Similar to vehicle but focused on inspection. CURRENCY FLOWS: - MXN → MXN: Buyer deposits via SPEI, seller receives SPEI payout (Route A1) - USD → MXN: Buyer wires USD, seller receives MXN SPEI payout (Route A2) - USD → USD: Buyer wires USD, seller receives USD wire payout (Route A3) - MXN → USD: Buyer deposits MXN SPEI, seller receives USD wire (Route A4) IMPORTANT CONSTRAINTS: - For MXN payouts: seller MUST have a beneficiary_clabe (18-digit CLABE) registered BEFORE release. The seller registers it via their dashboard — do NOT ask the buyer for it. - For USD payouts: seller MUST register a US bank account (external_account_id) via Bitso before release. - Seller MUST complete KYC verification before funds can be released. - NOT for crypto/wallet-to-wallet payments — use create_web3_escrow instead.. It is categorised as a Write tool in the Kustodia Escrow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kustodia Escrow MCP server in PolicyLayer and add a rule for create_escrow: 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.
create_escrow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_escrow 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 create_escrow. 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.
create_escrow 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.