gala_launchpad_fetch_all_price_history
Fetch all historical price snapshots for DEX tokens from the DEX Backend API with automatic pagination. Endpoint: /market/price-series (swap backend, read through gswap-sdk; the backend answers the whole series at once) Requirements: - DEX Backend API must be configured (dexBackendBaseUrl in SDK ...
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-fetch-all-price-history.md
What gala_launchpad_fetch_all_price_history does on Gala
AI agents call gala_launchpad_fetch_all_price_history 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 |
|---|---|---|---|
to | string | — | End date for filtering (ISO 8601 format, defaults to now). |
from | string | — | Start date for filtering (ISO 8601 format, defaults to 30 days ago). |
tokenId | object | — | Token identifier (string or TokenClassKey object). Use this OR tokenName, not both. |
sortOrder | string | — | Sort order for results (default: DESC for newest-first). |
tokenName | string | — | Simple token name for convenience (e.g., "demonkpop", "shoewars") - automatically resolves to full token ID. Use this OR tokenId, not both. |
Parameters from the server's own tool schema.
Why gala_launchpad_fetch_all_price_history is rated Low
Even though gala_launchpad_fetch_all_price_history 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_all_price_history 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_all_price_history, this is the rule to start with:
gala_launchpad_fetch_all_price_history 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_all_price_history call is checked against it from then on.
Questions about gala_launchpad_fetch_all_price_history
Fetch all historical price snapshots for DEX tokens from the DEX Backend API with automatic pagination. Endpoint: /market/price-series (swap backend, read through gswap-sdk; the backend answers the whole series at once) Requirements: - DEX Backend API must be configured (dexBackendBaseUrl in SDK config) - Either tokenName OR tokenId is required (not both) Token Identification: - Use tokenName for convenience (e.g., "demonkpop") - automatically resolved to full token ID - Use tokenId for direct specification (e.g., "Token|Unit|DKP|eth:...") - Provide exactly ONE of these parameters Use Cases: - Complete historical price analysis and charting - Full price trend identification over time periods - Comprehensive volatility analysis - Data export for external analytics Performance: API-based queries with automatic pagination (max 100 items per page, combined into single result). It is categorised as a Read tool in the Gala MCP Server, which means it retrieves data without modifying state.
gala_launchpad_fetch_all_price_history accepts 5 parameters: to, from, tokenId, sortOrder, tokenName. 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_all_price_history: 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_all_price_history 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_all_price_history 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_all_price_history. 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_all_price_history 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