sap_meteora_build_launchpad_migration

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp

High RISK CLASS

Category Execute

Parameters 43 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-meteora-build-launchpad-migration.md

WHAT IT DOES

What sap_meteora_build_launchpad_migration does on Sap

AI agents invoke sap_meteora_build_launchpad_migration 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
`payer`	string	Yes	Wallet paying for and authorizing migration.
`dammConfig`	string	—	Optional expected DAMM v2 config. The gateway always derives the authoritative address from the DBC pool config.
`poolAddress`	string	Yes	Original Meteora DBC pool address.
`latestBlockhash`	string	Yes	Fresh Solana blockhash supplied by the caller.

Parameters from the server's own tool schema.

RISK

Why sap_meteora_build_launchpad_migration is rated High

Constructs blockchain transactions affecting NFT positions and financial assets with external signing requirements.

From the tool's definition Build unsigned transaction, migration, Position NFT ephemerals, co-signed

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sap_meteora_build_launchpad_migration 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_meteora_build_launchpad_migration, this is the rule to start with:

sap_meteora_build_launchpad_migration Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sap_meteora_build_launchpad_migration": {
      "limits": [
        {
          "counter": "sap_meteora_build_launchpad_migration_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_meteora_build_launchpad_migration call is checked against it from then on.

FAQ

Questions about sap_meteora_build_launchpad_migration

What does the sap_meteora_build_launchpad_migration tool do? +

Build an unsigned official Meteora DBC to DAMM v2 migration after the curve reaches its threshold. The destination must be server-allowlisted. Position NFT ephemerals are co-signed; the payer remains the only external signer. Never broadcasts. 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_meteora_build_launchpad_migration accept? +

sap_meteora_build_launchpad_migration accepts 4 parameters: payer, dammConfig, poolAddress, latestBlockhash. Required: payer, poolAddress, latestBlockhash. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_meteora_build_launchpad_migration? +

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

sap_meteora_build_launchpad_migration is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sap_meteora_build_launchpad_migration? +

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

Set action: deny in the PolicyLayer policy for sap_meteora_build_launchpad_migration. 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_meteora_build_launchpad_migration? +

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

KEEP EXPLORING

More on Sap, and thousands of servers like it.

This server

All 453 Sap tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →