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

orca_swap

Swap tokens on an Orca Whirlpool. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent pro...

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

What orca_swap does on Sap

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

ParameterTypeRequiredDescription
amount string Yes Raw token amount (smallest unit)
wallet string Yes Solana public key (base58)
inputMint string Yes Token mint address (base58)
poolAddress string Yes Solana public key (base58)
slippageBps number Slippage Bps pagination control for Orca Swap.
isExactInput boolean Is Exact Input parameter for Orca Swap.

Parameters from the server's own tool schema.

Why orca_swap is rated Critical

Swapping tokens is a financial operation that moves real crypto assets on-chain.

From the tool's definition Swap tokens on an Orca Whirlpool

Questions about orca_swap

What does the orca_swap tool do? +

Swap tokens on an Orca Whirlpool. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. 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: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial. 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 orca_swap accept? +

orca_swap accepts 6 parameters: amount, wallet, inputMint, poolAddress, slippageBps, isExactInput. Required: amount, wallet, inputMint, poolAddress. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on orca_swap? +

Register the Sap MCP server in PolicyLayer and add a rule for orca_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.

What risk level is orca_swap? +

orca_swap 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 orca_swap? +

Yes. Add a rate_limit block to the orca_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.

How do I block orca_swap completely? +

Set action: deny in the PolicyLayer policy for orca_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.

What MCP server provides orca_swap? +

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

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