jupiter_swapInstructions

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

High RISK CLASS

Category Execute

Parameters 102 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/jupiter-swapinstructions.md

WHAT IT DOES

What jupiter_swapInstructions does on Sap

AI agents invoke jupiter_swapInstructions 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
`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 Instructions.
`wrapAndUnwrapSol`	boolean	—	Wrap And Unwrap Sol parameter for Jupiter Swap Instructions.
`useSharedAccounts`	boolean	—	Use Shared Accounts parameter for Jupiter Swap Instructions.
`asLegacyTransaction`	boolean	—	As Legacy Transaction transaction payload used by Jupiter Swap Instructions.
`destinationTokenAccount`	string	—	Solana wallet public key (base58)
`dynamicComputeUnitLimit`	boolean	—	Dynamic Compute Unit Limit controlling the maximum number of results returned by Jupiter Swap Instructions.
`computeUnitPriceMicroLamports`	number	—	Compute Unit Price Micro Lamports value to use for Jupiter Swap Instructions.

Parameters from the server's own tool schema.

RISK

Why jupiter_swapInstructions is rated High

Generates swap instructions for DeFi trading; execution depends on composition with financial transactions.

From the tool's definition swap instructions, composing, trading workflow, value-action

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

jupiter_swapInstructions Rate-limited

jupiter_swapInstructions 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": {
    "jupiter_swapInstructions": {
      "limits": [
        {
          "counter": "jupiter_swapinstructions_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 jupiter_swapInstructions call is checked against it from then on.

FAQ

Questions about jupiter_swapInstructions

What does the jupiter_swapInstructions tool do? +

Get individual swap instructions instead of a full transaction. Useful for composing with other instructions. 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 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 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 jupiter_swapInstructions accept? +

jupiter_swapInstructions accepts 10 parameters: feeAccount, quoteResponse, userPublicKey, useTokenLedger, wrapAndUnwrapSol, useSharedAccounts, asLegacyTransaction, destinationTokenAccount, dynamicComputeUnitLimit, 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_swapInstructions? +

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

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

Can I rate-limit jupiter_swapInstructions? +

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

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

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