gala_launchpad_remove_liquidity

Remove current-contract GSwap liquidity and return confirm() output.

SERVERGala SOURCE@gala-chain/gala-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 96 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-remove-liquidity.md

WHAT IT DOES

What gala_launchpad_remove_liquidity does on Gala

AI agents call gala_launchpad_remove_liquidity to permanently remove resources in Gala, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`fee`	number	Yes	Fee tier in basis points: 500 (0.05%), 3000 (0.30%), 10000 (1.00%).
`token0`	string	Yes	First token in pair (e.g., "GALA" or "GALA\|Unit\|none\|none").
`token1`	string	Yes	Second token in pair (e.g., "GUSDC" or "Token\|Unit\|GUSDC\|client:xxx").
`amount0`	string	—	Amount in standard decimal format (e.g., "1" for 1 GALA)
`amount1`	string	—	Amount in standard decimal format (e.g., "1" for 1 GALA)
`liquidity`	string	—	Amount in standard decimal format (e.g., "1" for 1 GALA)
`tickLower`	number	Yes	Lower tick boundary of the position.
`tickUpper`	number	Yes	Upper tick boundary of the position.
`ownerAddress`	string	Yes	Wallet address that owns the position: client\|<id>, eth\|<address> (the 40 hex digits, no 0x: eth\|0x<address> is not a valid form), 0x<address> or the 40 hex dig

Parameters from the server's own tool schema.

RISK

Why gala_launchpad_remove_liquidity is rated Critical

An AI agent that decides to call gala_launchpad_remove_liquidity doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Gala is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gala_launchpad_remove_liquidity Hidden

gala_launchpad_remove_liquidity is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "gala_launchpad_remove_liquidity"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about gala_launchpad_remove_liquidity

What does the gala_launchpad_remove_liquidity tool do? +

Remove current-contract GSwap liquidity and return confirm() output. It is categorised as a Destructive tool in the Gala MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does gala_launchpad_remove_liquidity accept? +

gala_launchpad_remove_liquidity accepts 9 parameters: fee, token0, token1, amount0, amount1, liquidity, tickLower, tickUpper, ownerAddress. Required: fee, token0, token1, tickLower, tickUpper, ownerAddress. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gala_launchpad_remove_liquidity? +

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

What risk level is gala_launchpad_remove_liquidity? +

gala_launchpad_remove_liquidity is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gala_launchpad_remove_liquidity? +

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

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

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

KEEP EXPLORING

More on Gala, and thousands of servers like it.

This server

All 324 Gala tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →