sap_adrena_build_add_limit_order

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

Critical RISK CLASS

Category Financial

Parameters 87 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-add-limit-order.md

WHAT IT DOES

What sap_adrena_build_add_limit_order does on Sap

AI agents use sap_adrena_build_add_limit_order 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	Order side.
`owner`	string	Yes	Order owner wallet public key (base58).
`leverage`	number	Yes	Leverage multiplier.
`limitPriceUsd`	number	—	Optional limit price cap. Omit for market price at fill.
`principalToken`	string	Yes	Asset to trade.
`collateralToken`	string	Yes	Collateral token.
`triggerPriceUsd`	number	Yes	Trigger price in USD. Order fills when oracle reaches this price.
`collateralAmount`	number	Yes	Collateral amount in human-readable units.

Parameters from the server's own tool schema.

RISK

Why sap_adrena_build_add_limit_order is rated Critical

Places financial limit orders on a DeFi trading platform, committing funds at trigger price.

From the tool's definition place a limit order on Adrena... fills when oracle price reaches trigger price

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_adrena_build_add_limit_order Approval-gated

Any call to sap_adrena_build_add_limit_order 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_add_limit_order": {
      "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_add_limit_order call is checked against it from then on.

FAQ

Questions about sap_adrena_build_add_limit_order

What does the sap_adrena_build_add_limit_order tool do? +

Build an unsigned transaction to place a limit order on Adrena. The order fills when the oracle price reaches the trigger price. Returns transactionBase64 only after builder-side RPC simulation passes. Show approval only when safeToApprove=true and approvalBlocked=false; otherwise 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.

What parameters does sap_adrena_build_add_limit_order accept? +

sap_adrena_build_add_limit_order accepts 8 parameters: side, owner, leverage, limitPriceUsd, principalToken, collateralToken, triggerPriceUsd, collateralAmount. Required: side, owner, leverage, principalToken, collateralToken, triggerPriceUsd, 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_add_limit_order? +

Register the Sap MCP server in PolicyLayer and add a rule for sap_adrena_build_add_limit_order: 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_add_limit_order? +

sap_adrena_build_add_limit_order 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_add_limit_order? +

Yes. Add a rate_limit block to the sap_adrena_build_add_limit_order 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_add_limit_order completely? +

Set action: deny in the PolicyLayer policy for sap_adrena_build_add_limit_order. 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_add_limit_order? +

sap_adrena_build_add_limit_order 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 453 Sap tools → Critical-risk tools on this server →

Across the catalogue

place_limit_order on Lighter MCP →place_order on MCP MetaTrader 4 Server →place_order on A2a Demos →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 →