sap_adrena_build_position_package
Build a single unsigned transaction that atomically opens a perp position AND sets stop loss AND take profit in one transaction. 1 payment, 1 signing, 1 submit — instead of 3 separate calls. If stopLossPriceUsd or takeProfitPriceUsd is omitted, that instruction is skipped. Returns transactionBase...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-adrena-build-position-package.md
What sap_adrena_build_position_package does on Sap
AI agents invoke sap_adrena_build_position_package to trigger actions in Sap. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
side | string | Yes | Position side. |
owner | string | Yes | Position owner wallet public key (base58). |
leverage | number | Yes | Leverage multiplier (e.g. 3 = 3x). |
priceUsd | number | — | Optional limit price in USD for the open. Omit for market order. |
principalToken | string | Yes | Asset to trade. |
collateralToken | string | Yes | Collateral token. USDC for shorts, match principal for longs. |
collateralAmount | number | Yes | Collateral amount in human-readable units. |
stopLossPriceUsd | number | — | Optional stop loss trigger price in USD. Omit to skip. |
takeProfitPriceUsd | number | — | Optional take profit trigger price in USD. Omit to skip. |
Parameters from the server's own tool schema.
Why sap_adrena_build_position_package is rated High
Constructs financial transactions that execute derivatives trading operations with externally-dependent effects requiring user signing.
From the tool's definition opens perp position, sets stop loss, take profit, unsigned transaction builder
Attacks that exploit this kind of access
The rule that runs sap_adrena_build_position_package 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_position_package, this is the rule to start with:
sap_adrena_build_position_package stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 sap_adrena_build_position_package call is checked against it from then on.
Questions about sap_adrena_build_position_package
Build a single unsigned transaction that atomically opens a perp position AND sets stop loss AND take profit in one transaction. 1 payment, 1 signing, 1 submit — instead of 3 separate calls. If stopLossPriceUsd or takeProfitPriceUsd is omitted, that instruction is skipped. Returns transactionBase64 for local signing via sap_payments_finalize_transaction. Includes balanceCheck. 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 Execute tool in the Sap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
sap_adrena_build_position_package accepts 9 parameters: side, owner, leverage, priceUsd, principalToken, collateralToken, collateralAmount, stopLossPriceUsd, takeProfitPriceUsd. Required: side, 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_position_package: 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_position_package is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sap_adrena_build_position_package 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_position_package. 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_position_package 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