sap_finalize_settlement_v2

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

Critical RISK CLASS

Category Financial

Parameters 40 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-finalize-settlement-v2.md

WHAT IT DOES

What sap_finalize_settlement_v2 does on Sap

AI agents use sap_finalize_settlement_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)
`depositorWallet`	string	—	Depositor wallet public key (base58)
`settlementIndex`	string	—	Settlement index to finalize (as a decimal string)

Parameters from the server's own tool schema.

RISK

Why sap_finalize_settlement_v2 is rated Critical

Finalizes financial settlements and payments requiring signer authorization with irreversible transaction effects.

From the tool's definition finalize settlement, payment flow, escrow, signer mode, paid value-action

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_finalize_settlement_v2 Approval-gated

Any call to sap_finalize_settlement_v2 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_finalize_settlement_v2": {
      "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_finalize_settlement_v2 call is checked against it from then on.

FAQ

Questions about sap_finalize_settlement_v2

What does the sap_finalize_settlement_v2 tool do? +

Local-signer-only direct finalization of a V2 pending settlement. Hosted users should call sap_escrow_build_finalize_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_finalize_settlement_v2 accept? +

sap_finalize_settlement_v2 accepts 4 parameters: nonce, agentWallet, depositorWallet, settlementIndex. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_finalize_settlement_v2? +

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

sap_finalize_settlement_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_finalize_settlement_v2? +

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

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

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

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

All critical-risk MCP tools → The MCP Attack Database →

Guides

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