jupiter_getDCAOrders
Get all DCA orders (active and optionally historical) for a wallet. 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...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/jupiter-getdcaorders.md
What jupiter_getDCAOrders does on Sap
AI agents call jupiter_getDCAOrders to retrieve information from Sap without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | Page pagination control for Jupiter Get D C A Orders. |
user | string | Yes | Wallet address to query (sent as "user" query param to Jupiter) |
limit | number | — | Limit controlling the maximum number of results returned by Jupiter Get D C A Orders. |
inputMint | string | — | Token mint address (base58) |
outputMint | string | — | Token mint address (base58) |
orderStatus | string | Yes | Filter by order status: "active" for running orders, "history" for completed/cancelled |
recurringType | string | Yes | Recurring order type — "time" for time-based DCA, "price" for price-triggered, "all" for both |
includeFailedTx | boolean | — | Include failed transactions in results (default: false) |
Parameters from the server's own tool schema.
Why jupiter_getDCAOrders is rated Low
Retrieves wallet order data without modification or financial transaction execution.
From the tool's definition Get all DCA orders for a wallet; read/discovery workflow
Attacks that exploit this kind of access
The rule that runs jupiter_getDCAOrders 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_getDCAOrders, this is the rule to start with:
jupiter_getDCAOrders is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every jupiter_getDCAOrders call is checked against it from then on.
Questions about jupiter_getDCAOrders
Get all DCA orders (active and optionally historical) for a wallet. 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: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. 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 Read tool in the Sap MCP Server, which means it retrieves data without modifying state.
jupiter_getDCAOrders accepts 8 parameters: page, user, limit, inputMint, outputMint, orderStatus, recurringType, includeFailedTx. Required: user, orderStatus, recurringType. 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_getDCAOrders: 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_getDCAOrders is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the jupiter_getDCAOrders 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_getDCAOrders. 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_getDCAOrders 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.
This server
Across the catalogue