spl-token_mintTo

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

High RISK CLASS

Category Execute

Parameters 44 required

Recommended Rate-limitedsee 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-mintto.md

WHAT IT DOES

What spl-token_mintTo does on Sap

AI agents invoke spl-token_mintTo to trigger actions in Sap. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`mint`	string	Yes	Token mint address
`amount`	string	Yes	Amount to mint (raw, smallest unit)
`destination`	string	Yes	Wallet to receive minted tokens
`mintAuthority`	string	Yes	Mint authority wallet

Parameters from the server's own tool schema.

RISK

Why spl-token_mintTo is rated High

spl-token_mintTo triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAccepts file system path (destination)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

spl-token_mintTo Rate-limited

spl-token_mintTo stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "spl-token_mintTo": {
      "limits": [
        {
          "counter": "spl-token_mintto_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT 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_mintTo call is checked against it from then on.

FAQ

Questions about spl-token_mintTo

What does the spl-token_mintTo tool do? +

Mint additional tokens to a destination wallet (requires mint authority). 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 Execute tool in the Sap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does spl-token_mintTo accept? +

spl-token_mintTo accepts 4 parameters: mint, amount, destination, mintAuthority. Required: mint, amount, destination, mintAuthority. The full parameter table on this page comes from the server's own tool schema.

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

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

spl-token_mintTo is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit spl-token_mintTo? +

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

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

spl-token_mintTo 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 → High-risk tools on this server →

Across the catalogue

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

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →