magicblock_transfer

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

Critical RISK CLASS

Category Financial

Parameters 125 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/magicblock-transfer.md

WHAT IT DOES

What magicblock_transfer does on Sap

AI agents use magicblock_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
`to`	string	Yes	Recipient wallet pubkey
`from`	string	Yes	Sender wallet pubkey
`memo`	string	—	Optional memo appended to the transaction
`mint`	string	Yes	SPL mint pubkey
`split`	number	—	Private only. Number of queue entries to split across (1-15, default 1)
`amount`	number	Yes	Base-unit amount to transfer (integer, minimum 1)
`legacy`	boolean	—	Skip lookup-table compilation, return a legacy transaction (default false)
`cluster`	string	—	Cluster: 'mainnet', 'devnet', or custom RPC URL
`gasless`	boolean	—	When true, uses configured sponsor as fee payer (default false)
`authToken`	string	—	Bearer token from login (required for private transfers)
`toBalance`	string	Yes	Where the recipient should receive funds
`validator`	string	—	Optional ER validator pubkey

Parameters from the server's own tool schema.

RISK

Why magicblock_transfer is rated Critical

Moves cryptocurrency tokens and commits financial obligations via blockchain transactions.

From the tool's definition SPL token transfer, payments finalize transaction, builder fee applies.

Risk signalsHigh parameter count (20 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

magicblock_transfer Approval-gated

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

FAQ

Questions about magicblock_transfer

What does the magicblock_transfer tool do? +

Build an unsigned SPL token transfer (public or private) through an Ephemeral Rollup. Supports base/ephemeral source and destination, delayed settlement, split transfers, and gasless mode. Private mode defaults: minDelayMs=0, maxDelayMs=0, split=1 — override for delayed or split settlements. Then use sap_preview_transaction, sap_sign_transaction, and sap_submit_signed_transaction — or use sap_payments_finalize_transaction for 1-call preview+sign+submit (hosted mode). Builder fee applies. SAP MCP execution guidance: Intent: local-signer write workflow. 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 magicblock_transfer accept? +

magicblock_transfer accepts 12 parameters: to, from, memo, mint, split, amount, legacy, cluster, gasless, authToken, toBalance, validator. Required: to, from, mint, amount, toBalance. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on magicblock_transfer? +

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

magicblock_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 magicblock_transfer? +

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

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

magicblock_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 → All critical-risk MCP tools → The MCP Attack Database →

Guides

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