gala_launchpad_flush_cache_wallet_aliases

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

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-flush-cache-wallet-aliases.md

WHAT IT DOES

What gala_launchpad_flush_cache_wallet_aliases does on Gala

AI agents call gala_launchpad_flush_cache_wallet_aliases 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
`address`	string	—	Optional wallet address (eth\|... or 0x... format). If omitted, ALL wallet-alias entries are flushed.

Parameters from the server's own tool schema.

RISK

Why gala_launchpad_flush_cache_wallet_aliases is rated Low

Even though gala_launchpad_flush_cache_wallet_aliases 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.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gala_launchpad_flush_cache_wallet_aliases Allowed

gala_launchpad_flush_cache_wallet_aliases is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gala_launchpad_flush_cache_wallet_aliases": {}
  }
}

ALLOW ONLY 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_flush_cache_wallet_aliases call is checked against it from then on.

FAQ

Questions about gala_launchpad_flush_cache_wallet_aliases

What does the gala_launchpad_flush_cache_wallet_aliases tool do? +

Flush wallet-alias cache entries (eth| → client| resolution cache). Clears the Redis cache that maps eth| addresses to their GalaChain client| aliases. Use this when a user's login returns a stale eth| address even though they have a client| alias on GalaChain. After flushing, the next login will re-resolve the alias from the GalaChain public-key contract. - Without address: flushes ALL wallet-alias entries (use after updating the public-key contract URL) - With address: flushes only the specified address's alias entry Use this when: - A user logs in and gets their eth| address instead of their client| alias - After fixing GALA_PUBLIC_KEY_CONTRACT configuration - After a GalaChain network outage caused null-cached aliases - Debugging alias resolution issues on dev/staging environments RETURNS: { flushedCount, duration, target? } - flushedCount: Number of alias cache entries flushed - duration: Time taken in milliseconds - target: Normalized address (only present when flushing a single address) Authentication: Requires streamAdminApiKey (admin) OR JWT auth as existing Overseer. It is categorised as a Read tool in the Gala MCP Server, which means it retrieves data without modifying state.

What parameters does gala_launchpad_flush_cache_wallet_aliases accept? +

gala_launchpad_flush_cache_wallet_aliases accepts 1 parameter: address. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gala_launchpad_flush_cache_wallet_aliases? +

Register the Gala MCP server in PolicyLayer and add a rule for gala_launchpad_flush_cache_wallet_aliases: 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_flush_cache_wallet_aliases? +

gala_launchpad_flush_cache_wallet_aliases is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gala_launchpad_flush_cache_wallet_aliases? +

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

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

gala_launchpad_flush_cache_wallet_aliases 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 →

Across the catalogue

cache_stats on ACE-MCP → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →