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

sap_adrena_build_cancel_limit_order

Build an unsigned transaction to cancel a limit order on Adrena. 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. Ro...

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp
High RISK CLASS
Category Execute
Parameters 33 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-cancel-limit-order.md

What sap_adrena_build_cancel_limit_order does on Sap

AI agents invoke sap_adrena_build_cancel_limit_order 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.

ParameterTypeRequiredDescription
owner string Yes Order owner wallet public key (base58).
orderId number Yes Limit order ID to cancel.
collateralToken string Yes Collateral token used for the order.

Parameters from the server's own tool schema.

Why sap_adrena_build_cancel_limit_order is rated High

Builds transaction that executes blockchain order cancellation; effects depend on order selection arguments.

From the tool's definition Build unsigned transaction to cancel limit order; returns transactionBase64

Questions about sap_adrena_build_cancel_limit_order

What does the sap_adrena_build_cancel_limit_order tool do? +

Build an unsigned transaction to cancel a limit order on Adrena. 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_cancel_limit_order accept? +

sap_adrena_build_cancel_limit_order accepts 3 parameters: owner, orderId, collateralToken. Required: owner, orderId, collateralToken. 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_cancel_limit_order? +

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

sap_adrena_build_cancel_limit_order 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_cancel_limit_order? +

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

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

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

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.