sap_adrena_build_open_short
Build an unsigned transaction to open or increase a short perp position on Adrena only after policy, balance, oracle-readiness, and simulation checks pass. Collateral must be USDC for shorts. Returns transactionBase64 only when safeToApprove=true, approvalBlocked=false, and the transaction passed...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-adrena-build-open-short.md
What sap_adrena_build_open_short does on Sap
AI agents use sap_adrena_build_open_short 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 |
|---|---|---|---|
owner | string | Yes | Position owner wallet public key (base58). |
leverage | number | Yes | Leverage multiplier. |
priceUsd | number | — | Optional limit price in USD. Omit for market order. |
principalToken | string | Yes | Asset to short. Supported: JITOSOL, WBTC, BONK. |
collateralToken | string | Yes | Collateral token. Must be USDC for shorts. |
collateralAmount | number | Yes | Collateral (USDC) amount in human-readable units. |
stopLossPriceUsd | number | — | Optional stop-loss price in USD. When provided, the policy engine treats this trade as having a stop loss. Omit to skip the SL requirement (if policy requires S |
Parameters from the server's own tool schema.
Why sap_adrena_build_open_short is rated Critical
Opens leveraged short perpetual positions, committing financial obligations with real collateral.
From the tool's definition open short perp position on Adrena, paid builder, collateral USDC
Attacks that exploit this kind of access
The rule that runs sap_adrena_build_open_short 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_build_open_short, this is the rule to start with:
Any call to sap_adrena_build_open_short 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_build_open_short call is checked against it from then on.
Questions about sap_adrena_build_open_short
Build an unsigned transaction to open or increase a short perp position on Adrena only after policy, balance, oracle-readiness, and simulation checks pass. Collateral must be USDC for shorts. Returns transactionBase64 only when safeToApprove=true, approvalBlocked=false, and the transaction passed pre-submit simulation. If oracleReadiness.ready=false, simulationError, safeToApprove is not true, or approvalBlocked appears, do not show approval and do not call finalize. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. 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_build_open_short accepts 7 parameters: owner, leverage, priceUsd, principalToken, collateralToken, collateralAmount, stopLossPriceUsd. Required: owner, leverage, principalToken, collateralToken, collateralAmount. 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_build_open_short: 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_build_open_short 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_build_open_short 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_build_open_short. 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_build_open_short 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