gala_launchpad_buy
Execute token purchase with slippage protection. WORKFLOW: 1. calculateBuyAmount() -> Get expected output (result.amount) 2. buy() -> Execute trade with expectedAmount (buys pay no reverse bonding curve fee) 3. fetchTrades() -> Verify trade completed - result.amount -> expectedAmount - maxAccepta...
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-buy.md
What gala_launchpad_buy does on Gala
AI agents invoke gala_launchpad_buy to trigger actions in Gala. 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 |
|---|---|---|---|
type | string | Yes | Trade type (must match what you used in calculateBuyAmount): - 'native': Spending GALA amount - 'exact': Buying exact token amount. |
amount | string | Yes | Amount to spend/buy. |
tokenName | string | Yes | Token name. |
privateKey | string | — | Optional private key override for this operation (format: "0x" + 64 hex characters). If provided, uses this wallet instead of the default MCP server wallet. |
expectedAmount | string | Yes | Expected token output amount from calculateBuyAmount (REQUIRED). CRITICAL: This is the 'amount' field from calculateBuyAmount result, NOT your input amount. W |
slippageToleranceFactor | number | Yes | Decimal format (0.05 = 5% slippage). |
maxAcceptableReverseBondingCurveFee | string | — | OPTIONAL: Base reverse bonding curve fee from calculateBuyAmount (GALA), result.reverseBondingCurveFee. Buys pay no reverse bonding curve fee, so this can be om |
maxAcceptableReverseBondingCurveFeeSlippageFactor | number | — | Optional slippage tolerance for reverse bonding curve fee (decimal, e.g., 0.01 for 1%). Defaults to 0.01 (1%) if not provided. Applied to maxAcceptableReverseBo |
Parameters from the server's own tool schema.
Why gala_launchpad_buy is rated High
gala_launchpad_buy triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs gala_launchpad_buy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gala, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gala_launchpad_buy, this is the rule to start with:
gala_launchpad_buy 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 Gala, apply this rule, and every gala_launchpad_buy call is checked against it from then on.
Questions about gala_launchpad_buy
Execute token purchase with slippage protection. WORKFLOW: 1. calculateBuyAmount() -> Get expected output (result.amount) 2. buy() -> Execute trade with expectedAmount (buys pay no reverse bonding curve fee) 3. fetchTrades() -> Verify trade completed - result.amount -> expectedAmount - maxAcceptableReverseBondingCurveFee is optional for a buy. RETURNS: Transaction details including input/output amounts and transaction ID. It is categorised as a Execute tool in the Gala MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
gala_launchpad_buy accepts 8 parameters: type, amount, tokenName, privateKey, expectedAmount, slippageToleranceFactor, maxAcceptableReverseBondingCurveFee, maxAcceptableReverseBondingCurveFeeSlippageFactor. Required: type, amount, tokenName, expectedAmount, slippageToleranceFactor. The full parameter table on this page comes from the server's own tool schema.
Register the Gala MCP server in PolicyLayer and add a rule for gala_launchpad_buy: 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 Gala. Nothing to install.
gala_launchpad_buy 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 gala_launchpad_buy 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 gala_launchpad_buy. 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.
gala_launchpad_buy is provided by the Gala MCP server (@gala-chain/gala-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gala, and thousands of servers like it.
This server
Across the catalogue