sap_adrena_trade_intent
Intent-level Adrena trading API. Pass market name, side, USD collateral, and leverage (or "max"). Resolves custody, collateral, prices, policy, balance, oracle-readiness, and simulation before returning a signable transaction. Never describe the result as ready-to-sign unless transactionBase64 ex...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-adrena-trade-intent.md
What sap_adrena_trade_intent does on Sap
AI agents use sap_adrena_trade_intent 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 |
|---|---|---|---|
side | string | Yes | Position side. |
owner | string | Yes | Wallet public key (base58). |
market | string | Yes | Market symbol: BONK, JITOSOL, WBTC, USDC, XAU, XAG, WTI. |
leverage | string | Yes | Leverage multiplier (e.g. "3" for 3x) or "max" for maxInitialLeverage. |
poolName | string | — | Pool: main-pool (default) or commodities-pool. |
stopLossPct | number | — | Optional stop loss as % from entry (e.g. 5 = 5% away). Omit to skip. |
collateralUsd | number | Yes | Collateral amount in USD. Converted to token amount using oracle price. |
takeProfitPct | number | — | Optional take profit as % from entry (e.g. 15 = 15% away). Omit to skip. |
Parameters from the server's own tool schema.
Why sap_adrena_trade_intent is rated Critical
Executes leveraged trading positions on Adrena protocol, directly committing financial obligations.
From the tool's definition Adrena trading API, leverage, open position, signable transaction
Attacks that exploit this kind of access
The rule that runs sap_adrena_trade_intent 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 sap_adrena_trade_intent, this is the rule to start with:
Any call to sap_adrena_trade_intent is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_adrena_trade_intent call is checked against it from then on.
Questions about sap_adrena_trade_intent
Intent-level Adrena trading API. Pass market name, side, USD collateral, and leverage (or "max"). Resolves custody, collateral, prices, policy, balance, oracle-readiness, and simulation before returning a signable transaction. Never describe the result as ready-to-sign unless transactionBase64 exists and no oracleReadiness.ready=false, simulationError, safeToApprove=false, or approvalBlocked field is present. 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 Financial tool in the Sap MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
sap_adrena_trade_intent accepts 8 parameters: side, owner, market, leverage, poolName, stopLossPct, collateralUsd, takeProfitPct. Required: side, owner, market, leverage, collateralUsd. 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 sap_adrena_trade_intent: 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.
sap_adrena_trade_intent is a Financial 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 sap_adrena_trade_intent 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 sap_adrena_trade_intent. 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.
sap_adrena_trade_intent 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