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

sap_escrow_build_create_transaction

Hosted-safe unsigned builder for create_escrow_v2. Use this from hosted SAP MCP, preview the result, then call local sap_payments_finalize_transaction with submit:true. The depositorWallet signs locally; keypair bytes never leave the user machine. Defaults to DisputeWindow settlementSecurity=2 an...

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp
Critical RISK CLASS
Category Financial
Parameters 120 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-escrow-build-create-transaction.md

What sap_escrow_build_create_transaction does on Sap

AI agents use sap_escrow_build_create_transaction to commit financial operations through Sap, usually the final step of a payment, billing, or trading workflow. A call moves real money.

ParameterTypeRequiredDescription
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
depositorWallet string Depositor wallet public key (base58). This wallet signs locally and funds the escrow; hosted SAP MCP never receives its private key.
disputeWindowSlots string Required positive dispute window in slots for settlementSecurity=2. Defaults to 2160 (~15 minutes).

Parameters from the server's own tool schema.

Why sap_escrow_build_create_transaction is rated Critical

Creates financial escrow transactions committing funds, constituting a financial obligation.

From the tool's definition create_escrow_v2, depositorWallet signs, escrow, payments

Risk signalsHigh parameter count (13 properties)

Questions about sap_escrow_build_create_transaction

What does the sap_escrow_build_create_transaction tool do? +

Hosted-safe unsigned builder for create_escrow_v2. Use this from hosted SAP MCP, preview the result, then call local sap_payments_finalize_transaction with submit:true. The depositorWallet signs locally; keypair bytes never leave the user machine. Defaults to DisputeWindow settlementSecurity=2 and rejects SelfReport/0. SAP MCP context: Hosted-safe unsigned Escrow V2 builder. The output is not submitted and is not signed by hosted SAP MCP. Preview it, then call local sap_payments_finalize_transaction with submit:true and confirm:true. Never create temporary signing scripts or read keypair JSON. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: hosted-safe builder. If a transaction is returned, preview/sign/submit with sap_payments_finalize_transaction; never create temporary signing scripts. 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.

What parameters does sap_escrow_build_create_transaction accept? +

sap_escrow_build_create_transaction accepts 12 parameters: nonce, arbiter, coSigner, maxCalls, expiresAt, tokenMint, agentWallet, pricePerCall, tokenDecimals, initialDeposit, depositorWallet, disputeWindowSlots. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_escrow_build_create_transaction? +

Register the Sap MCP server in PolicyLayer and add a rule for sap_escrow_build_create_transaction: 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.

What risk level is sap_escrow_build_create_transaction? +

sap_escrow_build_create_transaction 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 sap_escrow_build_create_transaction? +

Yes. Add a rate_limit block to the sap_escrow_build_create_transaction 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 sap_escrow_build_create_transaction completely? +

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

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

// 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 Sap'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.