jupiter_createLimitOrder

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

Critical RISK CLASS

Category Financial

Parameters 96 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-createlimitorder.md

WHAT IT DOES

What jupiter_createLimitOrder does on Sap

AI agents use jupiter_createLimitOrder 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
`maker`	string	Yes	Wallet address of the order creator
`payer`	string	Yes	Wallet paying for transaction fees
`feeBps`	number	—	Referral fee in bps
`expiredAt`	string	—	ISO 8601 expiry timestamp
`inputMint`	string	Yes	Input token mint
`outputMint`	string	Yes	Output token mint
`makingAmount`	string	Yes	Amount of input token to sell
`takingAmount`	string	Yes	Amount of output token to receive
`computeUnitPrice`	string	—	Priority fee (µ-lamports/CU)

Parameters from the server's own tool schema.

RISK

Why jupiter_createLimitOrder is rated Critical

Creates financial limit orders committing funds; explicitly flagged as paid value-action.

From the tool's definition Create a limit order... paid value-action; preview cost and transaction effects

Attacks that exploit this kind of access

RECOMMENDED RULE

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

jupiter_createLimitOrder Approval-gated

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

FAQ

Questions about jupiter_createLimitOrder

What does the jupiter_createLimitOrder tool do? +

Create a limit order. Returns an unsigned transaction — sign and submit via executeTrigger. 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_createLimitOrder accept? +

jupiter_createLimitOrder accepts 9 parameters: maker, payer, feeBps, expiredAt, inputMint, outputMint, makingAmount, takingAmount, computeUnitPrice. Required: maker, payer, inputMint, outputMint, makingAmount, takingAmount. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on jupiter_createLimitOrder? +

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

jupiter_createLimitOrder 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_createLimitOrder? +

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

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

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