gala_launchpad_fetch_swap_position_direct
Fetch one current-contract GSwap position by its compound pair and tick key.
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-fetch-swap-position-direct.md
What gala_launchpad_fetch_swap_position_direct does on Gala
AI agents call gala_launchpad_fetch_swap_position_direct to retrieve information from Gala without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| 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"). |
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.
Why gala_launchpad_fetch_swap_position_direct is rated Low
Even though gala_launchpad_fetch_swap_position_direct only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs gala_launchpad_fetch_swap_position_direct 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_fetch_swap_position_direct, this is the rule to start with:
gala_launchpad_fetch_swap_position_direct is read-only, so it stays allowed. 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_fetch_swap_position_direct call is checked against it from then on.
Questions about gala_launchpad_fetch_swap_position_direct
Fetch one current-contract GSwap position by its compound pair and tick key. It is categorised as a Read tool in the Gala MCP Server, which means it retrieves data without modifying state.
gala_launchpad_fetch_swap_position_direct accepts 6 parameters: fee, token0, token1, 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.
Register the Gala MCP server in PolicyLayer and add a rule for gala_launchpad_fetch_swap_position_direct: 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_fetch_swap_position_direct is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gala_launchpad_fetch_swap_position_direct 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_fetch_swap_position_direct. 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_fetch_swap_position_direct 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