magicblock_deposit

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

Critical RISK CLASS

Category Financial

Parameters 92 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-deposit.md

WHAT IT DOES

What magicblock_deposit does on Sap

AI agents use magicblock_deposit 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
`mint`	string	—	SPL mint. Defaults to USDC (mainnet) or devnet USDC
`owner`	string	Yes	Wallet pubkey that owns the tokens and will sign
`amount`	number	Yes	Base-unit amount to deposit (integer, minimum 1)
`cluster`	string	—	Cluster: 'mainnet', 'devnet', or custom RPC URL
`validator`	string	—	Optional ER validator pubkey. Defaults to the selected ephemeral RPC identity.
`idempotent`	boolean	—	Use idempotent variants for preparatory init instructions (default true)
`initIfMissing`	boolean	—	Initialize the transfer queue if missing (default true)
`initAtasIfMissing`	boolean	—	Initialize associated token accounts if missing (default true)
`initVaultIfMissing`	boolean	—	Initialize the vault if missing (default true)

Parameters from the server's own tool schema.

RISK

Why magicblock_deposit is rated Critical

Deposits cryptocurrency into rollup and incurs financial charges; moves money and commits financial obligations.

From the tool's definition deposit SPL tokens, builder fee applies, paid hosted call

Attacks that exploit this kind of access

RECOMMENDED RULE

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

magicblock_deposit Approval-gated

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

FAQ

Questions about magicblock_deposit

What does the magicblock_deposit tool do? +

Build an unsigned transaction to deposit SPL tokens from Solana into an Ephemeral Rollup. 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). Do not create local signing scripts. Builder fee applies. SAP MCP execution guidance: Intent: SAP MCP tool 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_deposit accept? +

magicblock_deposit accepts 9 parameters: mint, owner, amount, cluster, validator, idempotent, initIfMissing, initAtasIfMissing, initVaultIfMissing. Required: owner, amount. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on magicblock_deposit? +

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

magicblock_deposit 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_deposit? +

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

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

magicblock_deposit 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 →