sap_adrena_build_set_stop_loss

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

High RISK CLASS

Category Execute

Parameters 54 required

Recommended Rate-limitedsee 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-set-stop-loss.md

WHAT IT DOES

What sap_adrena_build_set_stop_loss does on Sap

AI agents invoke sap_adrena_build_set_stop_loss 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).
`principalToken`	string	Yes	Asset of the position.
`stopLossPriceUsd`	number	Yes	Stop loss trigger price in USD.
`closePositionPriceUsd`	number	—	Optional close position price in USD. If set, the position closes at this price when triggered.

Parameters from the server's own tool schema.

RISK

Why sap_adrena_build_set_stop_loss is rated High

Builds transactions that modify financial positions; execution depends on signing and network conditions.

From the tool's definition set stop loss on Adrena position, unsigned transaction builder

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_adrena_build_set_stop_loss Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sap_adrena_build_set_stop_loss": {
      "limits": [
        {
          "counter": "sap_adrena_build_set_stop_loss_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT 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_set_stop_loss call is checked against it from then on.

FAQ

Questions about sap_adrena_build_set_stop_loss

What does the sap_adrena_build_set_stop_loss tool do? +

Build an unsigned transaction to set stop loss on an Adrena position. Returns transactionBase64 for local signing. 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.

What parameters does sap_adrena_build_set_stop_loss accept? +

sap_adrena_build_set_stop_loss accepts 5 parameters: side, owner, principalToken, stopLossPriceUsd, closePositionPriceUsd. Required: side, owner, principalToken, stopLossPriceUsd. 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_set_stop_loss? +

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

sap_adrena_build_set_stop_loss is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sap_adrena_build_set_stop_loss? +

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

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

sap_adrena_build_set_stop_loss 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 → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →set_breakpoint on Frida Game Hacking MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →