gala_launchpad_list_global_flags
List ALL flags globally across all tokens with pagination and filtering. For overseers and admins to view flags across the entire platform. Use listFlags() for token-specific flag lists. Filter options: - tokenName: Filter to a specific token - contentType: Filter by CHAT_MESSAGE, COMMENT, or STR...
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-list-global-flags.md
What gala_launchpad_list_global_flags does on Gala
AI agents call gala_launchpad_list_global_flags 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 |
|---|---|---|---|
cursor | string | — | Cursor from previous response (omit for first page). |
reason | string | — | Filter by flag reason (optional) |
status | string | — | Filter by flag status: - PENDING: Not yet reviewed - DISMISSED: Reviewed, no action taken - ACTIONED: Reviewed, action was taken |
pageSize | integer | — | Results per page (default: 20, maximum: 100) |
tokenName | string | — | Filter by token name (optional - omit to show all tokens) |
contentType | string | — | Filter by content type (optional) |
reporterAddress | string | — | Filter by reporter address (optional) |
reportedUserAddress | string | — | Filter by reported user address (optional) |
Parameters from the server's own tool schema.
Why gala_launchpad_list_global_flags is rated Low
Even though gala_launchpad_list_global_flags 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
The rule that runs gala_launchpad_list_global_flags 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_list_global_flags, this is the rule to start with:
gala_launchpad_list_global_flags 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_list_global_flags call is checked against it from then on.
Questions about gala_launchpad_list_global_flags
List ALL flags globally across all tokens with pagination and filtering. For overseers and admins to view flags across the entire platform. Use listFlags() for token-specific flag lists. Filter options: - tokenName: Filter to a specific token - contentType: Filter by CHAT_MESSAGE, COMMENT, or STREAM - status: Filter by PENDING, DISMISSED, or ACTIONED - reason: Filter by flag reason (SPAM, HARASSMENT, etc.) - reporterAddress: Filter by who submitted the flag - reportedUserAddress: Filter by the content author Each flag includes an optional aiModeration field with AI analysis results when AI moderation is enabled. RETURNS: { flags: [{ ..., aiModeration?: { status, recommendation, confidence, summary, categories, reasoning, provider } }], pageInfo: { hasNextPage, endCursor } } Authentication: Requires streamAdminApiKey (admin) OR JWT auth (overseer). It is categorised as a Read tool in the Gala MCP Server, which means it retrieves data without modifying state.
gala_launchpad_list_global_flags accepts 8 parameters: cursor, reason, status, pageSize, tokenName, contentType, reporterAddress, reportedUserAddress. 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_list_global_flags: 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_list_global_flags 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_list_global_flags 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_list_global_flags. 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_list_global_flags 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