sap_adrena_build_swap
Build an unsigned transaction to swap tokens through an Adrena pool. Uses zero-slippage oracle pricing. Returns transactionBase64 only after builder-side RPC simulation passes. Show approval only when safeToApprove=true and approvalBlocked=false; otherwise do not call finalize. SAP MCP execution ...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-adrena-build-swap.md
What sap_adrena_build_swap does on Sap
AI agents invoke sap_adrena_build_swap 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 |
|---|---|---|---|
owner | string | Yes | Swapper wallet public key (base58). |
amount | number | Yes | Amount to swap in human-readable units. |
toToken | string | Yes | Token to swap to. |
fromToken | string | Yes | Token to swap from. |
minAmountOut | number | — | Minimum amount to receive (raw). 0 for no slippage protection. |
Parameters from the server's own tool schema.
Why sap_adrena_build_swap is rated High
Builds and simulates a token swap transaction; financial in nature but stops short of execution.
From the tool's definition Build an unsigned transaction to swap tokens through an Adrena pool
Attacks that exploit this kind of access
The rule that runs sap_adrena_build_swap 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_swap, this is the rule to start with:
sap_adrena_build_swap 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_adrena_build_swap call is checked against it from then on.
Questions about sap_adrena_build_swap
Build an unsigned transaction to swap tokens through an Adrena pool. Uses zero-slippage oracle pricing. Returns transactionBase64 only after builder-side RPC simulation passes. Show approval only when safeToApprove=true and approvalBlocked=false; otherwise do not call finalize. 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.
sap_adrena_build_swap accepts 5 parameters: owner, amount, toToken, fromToken, minAmountOut. Required: owner, amount, toToken, fromToken. 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_adrena_build_swap: 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_adrena_build_swap is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sap_adrena_build_swap 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_adrena_build_swap. 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_adrena_build_swap 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