sap_adrena_build_open_long

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp

Critical RISK CLASS

Category Financial

Parameters 75 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-adrena-build-open-long.md

WHAT IT DOES

What sap_adrena_build_open_long does on Sap

AI agents use sap_adrena_build_open_long 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). This is the fee payer and signer.
`leverage`	number	Yes	Leverage multiplier (e.g. 3 = 3x).
`priceUsd`	number	—	Optional limit price in USD. Omit for market order.
`principalToken`	string	Yes	Asset to trade (long). Supported: JITOSOL, WBTC, BONK.
`collateralToken`	string	Yes	Collateral token. Must match principal for longs. Supported: JITOSOL, WBTC, BONK.
`collateralAmount`	number	Yes	Collateral amount in human-readable units (e.g. 10 = 10 JITOSOL).
`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.

RISK

Why sap_adrena_build_open_long is rated Critical

Opens leveraged perpetual trading positions, committing financial obligations and market exposure.

From the tool's definition open or increase a long perp position on Adrena

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sap_adrena_build_open_long 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_long, this is the rule to start with:

sap_adrena_build_open_long Approval-gated

Any call to sap_adrena_build_open_long is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sap_adrena_build_open_long": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_adrena_build_open_long call is checked against it from then on.

FAQ

Questions about sap_adrena_build_open_long

What does the sap_adrena_build_open_long tool do? +

Build an unsigned transaction to open or increase a long perp position on Adrena. Returns transactionBase64 for local signing via sap_payments_finalize_transaction. The agent must sign locally — SAP MCP never signs user-owned perp transactions. 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.

What parameters does sap_adrena_build_open_long accept? +

sap_adrena_build_open_long 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.

How do I enforce a policy on sap_adrena_build_open_long? +

Register the Sap MCP server in PolicyLayer and add a rule for sap_adrena_build_open_long: 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.

What risk level is sap_adrena_build_open_long? +

sap_adrena_build_open_long is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit sap_adrena_build_open_long? +

Yes. Add a rate_limit block to the sap_adrena_build_open_long 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.

How do I block sap_adrena_build_open_long completely? +

Set action: deny in the PolicyLayer policy for sap_adrena_build_open_long. 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.

What MCP server provides sap_adrena_build_open_long? +

sap_adrena_build_open_long 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.

KEEP EXPLORING

More on Sap, and thousands of servers like it.

This server

All 375 Sap tools → Critical-risk tools on this server →

Across the catalogue

build_redeem_withdraw_tx on Atv → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →