sap_perp_trade_plan
Create a trader-grade perpetual futures plan from a simple intent. Returns notional size, stop risk, reward/risk, liquidation estimate, preflight checklist, and the exact SAP MCP read tools to call next. This is analysis-only: SAP MCP does not expose Adrena execution builders until they are IDL-b...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-perp-trade-plan.md
What sap_perp_trade_plan does on Sap
AI agents use sap_perp_trade_plan to create or update resources in Sap, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sap environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
side | string | Yes | Intended direction for the trade. |
notes | string | — | Optional user notes, catalyst, invalidation thesis, or strategy context. |
market | string | Yes | Perp market symbol or pair, for example SOL-PERP, BTC-PERP, or ETH-PERP. |
leverage | number | Yes | Requested leverage multiplier. Keep conservative unless user policy explicitly allows more. |
timeframe | string | — | Trading horizon such as scalp, intraday, swing, or hedge. |
entryPrice | number | Yes | Reference entry price in USD used for risk math. Required. Get the current price from sap_adrena_get_trading_prices or sap_adrena_get_prices before calling this |
stopLossPrice | number | — | Optional stop loss price in USD. Strongly recommended before execution. |
maxSlippageBps | number | — | Maximum execution slippage in basis points. Default 50 bps. |
takeProfitPrice | number | — | Optional take profit price in USD used to compute reward/risk. |
maxAccountRiskPct | number | — | Maximum account risk percentage allowed by local policy. Default 1%. |
collateralAmountUsd | number | Yes | Collateral to allocate in USD. This is the margin budget, not notional size. |
Parameters from the server's own tool schema.
Why sap_perp_trade_plan is rated Medium
An AI agent can call sap_perp_trade_plan faster than any human can review: one bad instruction and it creates or modifies resources in Sap by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs sap_perp_trade_plan 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_perp_trade_plan, this is the rule to start with:
sap_perp_trade_plan stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_perp_trade_plan call is checked against it from then on.
Questions about sap_perp_trade_plan
Create a trader-grade perpetual futures plan from a simple intent. Returns notional size, stop risk, reward/risk, liquidation estimate, preflight checklist, and the exact SAP MCP read tools to call next. This is analysis-only: SAP MCP does not expose Adrena execution builders until they are IDL-backed and locally finalizable. Required fields: market, side, collateralAmountUsd, leverage, entryPrice. Get entryPrice from sap_adrena_get_trading_prices or sap_adrena_get_prices before calling this tool. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: priced by hosted x402 challenge. 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 Write tool in the Sap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sap_perp_trade_plan accepts 11 parameters: side, notes, market, leverage, timeframe, entryPrice, stopLossPrice, maxSlippageBps, takeProfitPrice, maxAccountRiskPct, collateralAmountUsd. Required: side, market, leverage, entryPrice, collateralAmountUsd. 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_perp_trade_plan: 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_perp_trade_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sap_perp_trade_plan 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_perp_trade_plan. 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_perp_trade_plan 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