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

sap_deposit_escrow_v2

Local-signer-only direct deposit into a V2 escrow. Hosted users should call sap_escrow_build_deposit_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 a...

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp
Critical RISK CLASS
Category Financial
Parameters 30 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-deposit-escrow-v2.md

What sap_deposit_escrow_v2 does on Sap

AI agents use sap_deposit_escrow_v2 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 Escrow nonce (as a decimal string, default: 0)
amount string Deposit amount 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 token.
agentWallet string Agent wallet public key (base58)

Parameters from the server's own tool schema.

Why sap_deposit_escrow_v2 is rated Critical

Tool moves money into escrow with financial obligations and settlement effects.

From the tool's definition direct deposit into escrow; payment and settlement flow; pricing paid value-action

Questions about sap_deposit_escrow_v2

What does the sap_deposit_escrow_v2 tool do? +

Local-signer-only direct deposit into a V2 escrow. Hosted users should call sap_escrow_build_deposit_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.

What parameters does sap_deposit_escrow_v2 accept? +

sap_deposit_escrow_v2 accepts 3 parameters: nonce, amount, agentWallet. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_deposit_escrow_v2? +

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

What risk level is sap_deposit_escrow_v2? +

sap_deposit_escrow_v2 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_deposit_escrow_v2? +

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

How do I block sap_deposit_escrow_v2 completely? +

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

What MCP server provides sap_deposit_escrow_v2? +

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

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