spl-token_transfer

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

Critical RISK CLASS

Category Financial

Parameters 64 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/spl-token-transfer.md

WHAT IT DOES

What spl-token_transfer does on Sap

AI agents use spl-token_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 address
`from`	string	Yes	Sender wallet address
`memo`	string	—	Optional memo to attach to the transaction
`mint`	string	Yes	Token mint address
`amount`	string	Yes	Amount to transfer (raw, smallest unit)
`createAta`	boolean	—	Create recipient ATA if needed (default: true)

Parameters from the server's own tool schema.

RISK

Why spl-token_transfer is rated Critical

Moves cryptocurrency assets between wallets; irreversible token transfers constitute direct financial obligation.

From the tool's definition Transfer SPL tokens between wallets. Optionally creates recipient ATA.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

spl-token_transfer Approval-gated

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

FAQ

Questions about spl-token_transfer

What does the spl-token_transfer tool do? +

Transfer SPL tokens between wallets. Optionally creates the recipient ATA. SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle. SAP MCP execution guidance: Intent: local-signer write workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. 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 spl-token_transfer accept? +

spl-token_transfer accepts 6 parameters: to, from, memo, mint, amount, createAta. Required: to, from, mint, amount. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on spl-token_transfer? +

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

spl-token_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 spl-token_transfer? +

Yes. Add a rate_limit block to the spl-token_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 spl-token_transfer completely? +

Set action: deny in the PolicyLayer policy for spl-token_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 spl-token_transfer? +

spl-token_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 →