sap_close_escrow_v2
Local-signer-only direct close for an empty V2 escrow. Hosted users should call sap_escrow_build_close_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...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-close-escrow-v2.md
What sap_close_escrow_v2 does on Sap
AI agents use sap_close_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 | — | Escrow nonce (as a decimal string, default: 0) |
agentWallet | string | — | Agent wallet public key (base58) |
Parameters from the server's own tool schema.
Why sap_close_escrow_v2 is rated Critical
Closing an escrow finalizes financial settlement, committing or releasing funds irreversibly.
From the tool's definition Payment and settlement flow... close for an empty V2 escrow
Attacks that exploit this kind of access
The rule that runs sap_close_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_close_escrow_v2, this is the rule to start with:
Any call to sap_close_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_close_escrow_v2 call is checked against it from then on.
Questions about sap_close_escrow_v2
Local-signer-only direct close for an empty V2 escrow. Hosted users should call sap_escrow_build_close_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: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. 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_close_escrow_v2 accepts 2 parameters: nonce, agentWallet. 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_close_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_close_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_close_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_close_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_close_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