sap_perp_risk_check
Pre-trade dynamic risk gate. Reads the trade journal to compute daily P&L, drawdown, and cooldown status. Returns allowed/disallowed with a risk score (0-1) and recommendation (PROCEED/WAIT/BLOCK). Call this before sap_adrena_build_open_long or sap_adrena_build_open_short. Combines with the stati...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-perp-risk-check.md
What sap_perp_risk_check does on Sap
AI agents call sap_perp_risk_check to retrieve information from Sap without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
side | string | Yes | Position side. |
market | string | Yes | Market symbol (e.g. BONK, JITOSOL, WBTC, XAU). |
leverage | number | Yes | Leverage multiplier (e.g. 3 for 3x). |
collateralUsd | number | Yes | Collateral amount in USD. |
Parameters from the server's own tool schema.
Why sap_perp_risk_check is rated Low
Retrieves and analyzes trading data; produces advisory output with no state changes.
From the tool's definition Reads trade journal, computes P&L, returns risk score and recommendation.
Attacks that exploit this kind of access
The rule that runs sap_perp_risk_check 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_risk_check, this is the rule to start with:
sap_perp_risk_check is read-only, so it stays allowed. 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_risk_check call is checked against it from then on.
Questions about sap_perp_risk_check
Pre-trade dynamic risk gate. Reads the trade journal to compute daily P&L, drawdown, and cooldown status. Returns allowed/disallowed with a risk score (0-1) and recommendation (PROCEED/WAIT/BLOCK). Call this before sap_adrena_build_open_long or sap_adrena_build_open_short. Combines with the static policy engine for full risk management. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. 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 Read tool in the Sap MCP Server, which means it retrieves data without modifying state.
sap_perp_risk_check accepts 4 parameters: side, market, leverage, collateralUsd. Required: side, market, leverage, collateralUsd. 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_risk_check: 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_risk_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sap_perp_risk_check 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_risk_check. 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_risk_check 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