New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

sap_adrena_build_close_long

Build an unsigned transaction to close a long perp position on Adrena. Default closes 100% at market price. Returns transactionBase64 for local signing. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsi...

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp
Critical RISK CLASS
Category Financial
Parameters 42 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-close-long.md

What sap_adrena_build_close_long does on Sap

AI agents use sap_adrena_build_close_long to commit financial operations through Sap, usually the final step of a payment, billing, or trading workflow. A call moves real money.

ParameterTypeRequiredDescription
owner string Yes Position owner wallet public key (base58).
priceUsd number Optional close price in USD. Omit for market close.
percentage number Percentage to close (0-1000000, where 1000000 = 100%). Default 1000000.
principalToken string Yes Asset of the position. Supported: JITOSOL, WBTC, BONK.

Parameters from the server's own tool schema.

Why sap_adrena_build_close_long is rated Critical

Closes a leveraged perpetual trading position, directly committing financial transactions.

From the tool's definition close a long perp position on Adrena... paid builder

Questions about sap_adrena_build_close_long

What does the sap_adrena_build_close_long tool do? +

Build an unsigned transaction to close a long perp position on Adrena. Default closes 100% at market price. 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 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_close_long accept? +

sap_adrena_build_close_long accepts 4 parameters: owner, priceUsd, percentage, principalToken. Required: owner, principalToken. 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_close_long? +

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

sap_adrena_build_close_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_close_long? +

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

Set action: deny in the PolicyLayer policy for sap_adrena_build_close_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_close_long? +

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

More on Sap, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sap's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.