sap_escrow_build_settle_transaction

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp

Critical RISK CLASS

Category Financial

Parameters 60 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-settle-transaction.md

WHAT IT DOES

What sap_escrow_build_settle_transaction does on Sap

AI agents use sap_escrow_build_settle_transaction 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.
`coSigner`	string	—	Optional co-signer public key for CoSigned escrows when the escrow account requires it.
`agentWallet`	string	—	Agent owner wallet public key (base58). This wallet signs locally because settlement releases funds to the serving agent.
`serviceHash`	object	—	32-byte service/audit hash. Use a stable hash of the fulfilled paid work.
`callsToSettle`	string	—	Number of served calls to settle as a decimal string.
`depositorWallet`	string	—	Depositor wallet public key (base58) for the escrow being settled.

Parameters from the server's own tool schema.

RISK

Why sap_escrow_build_settle_transaction is rated Critical

Builds escrow settlement transactions that commit financial obligations between parties.

From the tool's definition settle_calls_v2, escrows, pending settlement PDA, coSigner

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sap_escrow_build_settle_transaction 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_escrow_build_settle_transaction, this is the rule to start with:

sap_escrow_build_settle_transaction Approval-gated

Any call to sap_escrow_build_settle_transaction is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sap_escrow_build_settle_transaction": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_escrow_build_settle_transaction call is checked against it from then on.

FAQ

Questions about sap_escrow_build_settle_transaction

What does the sap_escrow_build_settle_transaction tool do? +

Hosted-safe unsigned builder for settle_calls_v2. The agent owner wallet signs locally. DisputeWindow escrows create a pending settlement PDA; CoSigned escrows require the coSigner account when configured. 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_settle_transaction accept? +

sap_escrow_build_settle_transaction accepts 6 parameters: nonce, coSigner, agentWallet, serviceHash, callsToSettle, depositorWallet. 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_settle_transaction? +

Register the Sap MCP server in PolicyLayer and add a rule for sap_escrow_build_settle_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_settle_transaction? +

sap_escrow_build_settle_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_settle_transaction? +

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

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

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

KEEP EXPLORING

More on Sap, and thousands of servers like it.

This server

All 375 Sap tools → Critical-risk tools on this server →

Across the catalogue

build_redeem_withdraw_tx on Atv →bank_transaction_create on AbraFlexi → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →