sap_create_escrow_v2
Local-signer-only direct V2 escrow creation using SDK EscrowV2Module.create. Defaults to DisputeWindow settlementSecurity=2; SelfReport/0 is rejected. Hosted accountless SAP MCP rejects this before x402 payment; hosted users should call sap_escrow_build_create_transaction and finalize locally. SA...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-create-escrow-v2.md
What sap_create_escrow_v2 does on Sap
AI agents use sap_create_escrow_v2 to commit financial operations through Sap, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
nonce | string | — | Optional escrow nonce as a decimal string. Defaults to 0. |
arbiter | string | — | Optional arbiter public key kept for IDL compatibility and dispute workflows. |
coSigner | string | — | Required co-signer wallet public key when settlementSecurity=1 (CoSigned). |
maxCalls | string | — | Maximum number of calls covered by the escrow as a decimal string. Use 0 for unlimited when supported by policy. |
expiresAt | string | — | Optional expiry timestamp in unix seconds as a decimal string. Defaults to 0 (no expiry). |
tokenMint | string | — | Optional SPL payment token mint. Omit/null for native SOL. Use EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v for mainnet USDC x402 escrows. |
agentWallet | string | — | Agent owner wallet public key (base58). The V2 escrow PDA is derived from this wallet plus nonce. |
pricePerCall | string | — | Price per served call as a decimal string. Amount in the escrow token smallest unit: lamports for SOL, micro-USDC for USDC, or base units for the configured SPL |
tokenDecimals | number | — | Payment token decimals. Defaults to 6 when tokenMint is set, otherwise 9 for native SOL. |
initialDeposit | string | — | Initial escrow deposit as a decimal string. Amount in the escrow token smallest unit: lamports for SOL, micro-USDC for USDC, or base units for the configured SP |
disputeWindowSlots | string | — | Required positive dispute window in slots for settlementSecurity=2. Defaults to 2160 (~15 minutes). |
settlementSecurity | number | — | V2 settlement security mode. 1=CoSigned (requires coSigner). 2=DisputeWindow (recommended default; requires disputeWindowSlots > 0). SelfReport/0 is deprecated |
Parameters from the server's own tool schema.
Why sap_create_escrow_v2 is rated Critical
Creates financial escrow contracts involving payment obligations and settlement security.
From the tool's definition escrow creation, payment and settlement flow, paid value-action
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs sap_create_escrow_v2 safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sap_create_escrow_v2, this is the rule to start with:
Any call to sap_create_escrow_v2 is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_create_escrow_v2 call is checked against it from then on.
Questions about sap_create_escrow_v2
Local-signer-only direct V2 escrow creation using SDK EscrowV2Module.create. Defaults to DisputeWindow settlementSecurity=2; SelfReport/0 is rejected. Hosted accountless SAP MCP rejects this before x402 payment; hosted users should call sap_escrow_build_create_transaction and finalize locally. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial. It is categorised as a Financial tool in the Sap MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
sap_create_escrow_v2 accepts 12 parameters: nonce, arbiter, coSigner, maxCalls, expiresAt, tokenMint, agentWallet, pricePerCall, tokenDecimals, initialDeposit, disputeWindowSlots, settlementSecurity. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for sap_create_escrow_v2: 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 Sap. Nothing to install.
sap_create_escrow_v2 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 sap_create_escrow_v2 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 sap_create_escrow_v2. 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.
sap_create_escrow_v2 is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sap, and thousands of servers like it.
Across the catalogue