jupiter_cancelLimitOrders
Create unsigned transactions to cancel multiple limit orders in batch. 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 sig...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/jupiter-cancellimitorders.md
What jupiter_cancelLimitOrders does on Sap
AI agents call jupiter_cancelLimitOrders to permanently remove resources in Sap, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
maker | string | Yes | Solana wallet public key (base58) |
orders | array | Yes | Array of order public keys to cancel |
computeUnitPrice | string | — | Compute Unit Price parameter for Jupiter Cancel Limit Orders. |
Parameters from the server's own tool schema.
Why jupiter_cancelLimitOrders is rated Critical
An AI agent that decides to call jupiter_cancelLimitOrders doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Sap is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs jupiter_cancelLimitOrders 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_cancelLimitOrders, this is the rule to start with:
jupiter_cancelLimitOrders is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every jupiter_cancelLimitOrders call is checked against it from then on.
Questions about jupiter_cancelLimitOrders
Create unsigned transactions to cancel multiple limit orders in batch. 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 Destructive tool in the Sap MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
jupiter_cancelLimitOrders accepts 3 parameters: maker, orders, computeUnitPrice. Required: maker, orders. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for jupiter_cancelLimitOrders: 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.
jupiter_cancelLimitOrders is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the jupiter_cancelLimitOrders 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.
Set action: deny in the PolicyLayer policy for jupiter_cancelLimitOrders. 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.
jupiter_cancelLimitOrders 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.
More on Sap, and thousands of servers like it.
Across the catalogue