sap_build_sol_transfer

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-build-sol-transfer.md

WHAT IT DOES

What sap_build_sol_transfer does on Sap

AI agents use sap_build_sol_transfer 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
`lamports`	number	—	Amount in lamports (1 SOL = 1,000,000,000 lamports). Use sap_estimate_tool_cost to check the builder fee before calling.
`toPubkey`	string	—	Recipient public key in base58.
`fromPubkey`	string	—	Sender public key in base58. This is the fee payer and must sign the transaction locally.

Parameters from the server's own tool schema.

RISK

Why sap_build_sol_transfer is rated Critical

Builds unsigned cryptocurrency transfer transactions enabling value movement; highest severity due to financial impact.

From the tool's definition native SOL transfer transaction, move money, financial obligation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_build_sol_transfer Approval-gated

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

FAQ

Questions about sap_build_sol_transfer

What does the sap_build_sol_transfer tool do? +

Build an unsigned native SOL transfer transaction using SystemProgram.transfer. Returns serialized base64 transaction for the agent to sign locally with sap_payments_finalize_transaction or sap_sign_transaction → sap_submit_signed_transaction. This is the hosted-safe equivalent of spl-token_transferSol (which is local-signer-only and cannot run on the hosted accountless server). Builder fee applies. 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: 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.

What parameters does sap_build_sol_transfer accept? +

sap_build_sol_transfer accepts 3 parameters: lamports, toPubkey, fromPubkey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_build_sol_transfer? +

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

sap_build_sol_transfer 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_build_sol_transfer? +

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

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

sap_build_sol_transfer 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

bridge_transfer on 0xaibridge →build_redeem_withdraw_tx on Atv → All critical-risk MCP tools → The MCP Attack Database →

Guides

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