sap_sunrise_swap_intent
One-call Sunrise swap intent: resolves both token SYMBOLS to canonical mints, then fetches a quote with the user's wallets and returns the unsignedTransaction + quoteId + routeName + providerRequestId. The transaction is NOT broadcast — sign it locally and execute with sap_sunrise_execute_quote. ...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-sunrise-swap-intent.md
What sap_sunrise_swap_intent does on Sap
AI agents invoke sap_sunrise_swap_intent 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 |
|---|---|---|---|
toSymbol | string | Yes | Output token symbol |
toAddress | string | Yes | Wallet address receiving the output token |
fromAmount | string | Yes | Input amount as STRING in base units of the FROM token |
fromSymbol | string | Yes | Input token symbol (e.g. USDC, MON) |
fromAddress | string | Yes | Wallet address sending the input token |
Parameters from the server's own tool schema.
Why sap_sunrise_swap_intent is rated High
Prepares executable crypto swap transactions; AI could craft harmful trades despite unsigned requirement.
From the tool's definition swap intent, resolves tokens, fetches quote, returns unsignedTransaction, NOT broadcast
Attacks that exploit this kind of access
The rule that runs sap_sunrise_swap_intent 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_sunrise_swap_intent, this is the rule to start with:
sap_sunrise_swap_intent 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_sunrise_swap_intent call is checked against it from then on.
Questions about sap_sunrise_swap_intent
One-call Sunrise swap intent: resolves both token SYMBOLS to canonical mints, then fetches a quote with the user's wallets and returns the unsignedTransaction + quoteId + routeName + providerRequestId. The transaction is NOT broadcast — sign it locally and execute with sap_sunrise_execute_quote. BUILDER tier. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. 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_sunrise_swap_intent accepts 5 parameters: toSymbol, toAddress, fromAmount, fromSymbol, fromAddress. Required: toSymbol, toAddress, fromAmount, fromSymbol, fromAddress. 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_sunrise_swap_intent: 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_sunrise_swap_intent 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_sunrise_swap_intent 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_sunrise_swap_intent. 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_sunrise_swap_intent 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