jupiter_swap

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

Critical RISK CLASS

Category Financial

Parameters 122 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-swap.md

WHAT IT DOES

What jupiter_swap does on Sap

AI agents use jupiter_swap 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
`feeAccount`	string	—	Solana wallet public key (base58)
`quoteResponse`	object	Yes	The full quoteResponse object from getQuote
`userPublicKey`	string	Yes	Solana wallet public key (base58)
`useTokenLedger`	boolean	—	Use Token Ledger mint, symbol, or token identifier used by Jupiter Swap.
`dynamicSlippage`	boolean	—	Dynamic Slippage pagination control for Jupiter Swap.
`wrapAndUnwrapSol`	boolean	—	Auto wrap/unwrap SOL (default true)
`useSharedAccounts`	boolean	—	Use Shared Accounts parameter for Jupiter Swap.
`asLegacyTransaction`	boolean	—	As Legacy Transaction transaction payload used by Jupiter Swap.
`destinationTokenAccount`	string	—	Solana wallet public key (base58)
`dynamicComputeUnitLimit`	boolean	—	Dynamic Compute Unit Limit controlling the maximum number of results returned by Jupiter Swap.
`skipUserAccountsRpcCalls`	boolean	—	Skip User Accounts RPC Calls endpoint or RPC selector used by Jupiter Swap.
`computeUnitPriceMicroLamports`	number	—	Priority fee in µ-lamports/CU

Parameters from the server's own tool schema.

RISK

Why jupiter_swap is rated Critical

Executes token swaps involving real financial value on Solana blockchain.

From the tool's definition swap transaction, paid value-action, Solana trading workflow

Risk signalsHigh parameter count (12 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

jupiter_swap Approval-gated

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

FAQ

Questions about jupiter_swap

What does the jupiter_swap tool do? +

Build an unsigned swap transaction from a quote response. Sign and send the returned transaction. 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: Solana value-action or trading 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_swap accept? +

jupiter_swap accepts 12 parameters: feeAccount, quoteResponse, userPublicKey, useTokenLedger, dynamicSlippage, wrapAndUnwrapSol, useSharedAccounts, asLegacyTransaction, destinationTokenAccount, dynamicComputeUnitLimit, skipUserAccountsRpcCalls, computeUnitPriceMicroLamports. Required: quoteResponse, userPublicKey. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on jupiter_swap? +

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

jupiter_swap 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_swap? +

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

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

jupiter_swap 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

menese_swap on Mcp Menesesdk → All critical-risk MCP tools → The MCP Attack Database →

Guides

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