sap_perpspad_build_escrow_launch
Build an escrow-backed PerpsPad launch (creator-split Option B): derives the trustless escrow PDA from the NEW token mint, swaps the launch creatorAddress to that PDA, and returns the unsigned config + pool + initialize_escrow transactions. The hourly creator_payout then lands on the escrow PDA, ...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-perpspad-build-escrow-launch.md
What sap_perpspad_build_escrow_launch does on Sap
AI agents use sap_perpspad_build_escrow_launch to commit financial operations through Sap, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
legs | array | — | Optional 2-leg basket instead of single underlying. |
name | string | Yes | Coin display name |
quote | string | — | Pairing token: SOL (default), USDC, or CUSTOM |
devBuy | number | Yes | Dev-buy in quote units (SOL 0.1-5, USDC 5-5000) |
ticker | string | Yes | Coin ticker, A-Z 0-9 only (e.g. MOON) |
imageUrl | string | — | Optional coin image URL |
leverage | number | — | Leverage of the backing perp (1..market cap) |
direction | string | — | Side of the backing perp |
quoteMint | string | — | CUSTOM only: the SPL mint to pair against |
twitterUrl | string | — | Optional X/Twitter URL |
underlying | string | — | Single-perp market backing the coin (e.g. SOL, BTC, OIL). Provide underlying+leverage+direction OR legs. |
websiteUrl | string | — | Optional website URL |
Parameters from the server's own tool schema.
Why sap_perpspad_build_escrow_launch is rated Critical
Builds and initiates financial transactions with on-chain fund splits and escrow commitments.
From the tool's definition escrow launch, creator_payout, 70%/30% split, transactions, financial obligations
Risk signalsHigh parameter count (19 properties)
Attacks that exploit this kind of access
The rule that runs sap_perpspad_build_escrow_launch 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_perpspad_build_escrow_launch, this is the rule to start with:
Any call to sap_perpspad_build_escrow_launch is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_perpspad_build_escrow_launch call is checked against it from then on.
Questions about sap_perpspad_build_escrow_launch
Build an escrow-backed PerpsPad launch (creator-split Option B): derives the trustless escrow PDA from the NEW token mint, swaps the launch creatorAddress to that PDA, and returns the unsigned config + pool + initialize_escrow transactions. The hourly creator_payout then lands on the escrow PDA, which hard-splits 70% to the agent wallet / 30% to the OOBE treasury on-chain — non-custodial, permissionless. The mint keypair is generated by the CALLER (agent flow) and passed as mintKeypairSecret (64-byte array); the config tx materializes that exact mint. Agent wallet (70% destination) is stored immutably. Sign and send: initialize_escrow FIRST (agent wallet signs), then config, then pool. BUILDER tier. 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.
sap_perpspad_build_escrow_launch accepts 12 parameters: legs, name, quote, devBuy, ticker, imageUrl, leverage, direction, quoteMint, twitterUrl, underlying, websiteUrl. Required: name, devBuy, ticker. 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_perpspad_build_escrow_launch: 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_perpspad_build_escrow_launch is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sap_perpspad_build_escrow_launch 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_perpspad_build_escrow_launch. 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_perpspad_build_escrow_launch 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.
Across the catalogue