jupiter_smartSwap

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

Critical RISK CLASS

Category Financial

Parameters 124 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/jupiter-smartswap.md

WHAT IT DOES

What jupiter_smartSwap does on Sap

AI agents use jupiter_smartSwap 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
`amount`	string	Yes	Raw token amount to swap (in smallest unit, no decimals)
`swapMode`	string	—	Swap mode (default: ExactIn)
`inputMint`	string	Yes	Source token mint address
`feeAccount`	string	—	Solana wallet public key (base58)
`outputMint`	string	Yes	Destination token mint address
`maxAccounts`	number	—	Max accounts in transaction (default: 64)
`slippageBps`	number	—	Slippage tolerance in bps (e.g. 50 = 0.5%)
`userPublicKey`	string	Yes	Wallet public key that will sign the transaction
`platformFeeBps`	number	—	Platform fee in bps for referral revenue
`dynamicSlippage`	boolean	—	Enable dynamic slippage for better execution
`onlyDirectRoutes`	boolean	—	Restrict to single-hop routes for lower latency
`wrapAndUnwrapSol`	boolean	—	Auto wrap/unwrap SOL (default: true)

Parameters from the server's own tool schema.

RISK

Why jupiter_smartSwap is rated Critical

Initiates token swaps involving financial asset exchange between wallets.

From the tool's definition fetches a quote and builds swap instructions... preparing a swap

Risk signalsHigh parameter count (17 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

jupiter_smartSwap Approval-gated

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

FAQ

Questions about jupiter_smartSwap

What does the jupiter_smartSwap tool do? +

Smart Swap — all-in-one compound tool that fetches a quote and builds swap instructions in a single call. Provide input/output mints, amount, and wallet address to get back a quote, individual swap instructions, and a human-readable summary. The returned instructions can be assembled into a transaction and signed. This is the recommended entry-point for AI agents preparing a swap. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. 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 jupiter_smartSwap accept? +

jupiter_smartSwap accepts 12 parameters: amount, swapMode, inputMint, feeAccount, outputMint, maxAccounts, slippageBps, userPublicKey, platformFeeBps, dynamicSlippage, onlyDirectRoutes, wrapAndUnwrapSol. Required: amount, inputMint, outputMint, userPublicKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on jupiter_smartSwap? +

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

jupiter_smartSwap 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 jupiter_smartSwap? +

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

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

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