gala_launchpad_set_slow_mode
Set slow mode interval for a stream chat. Slow mode throttles users to one message per N seconds. Enforcement is server-side (Redis-backed rate limiting). Setting to 0 disables slow mode. Valid presets: 0 (off), 10, 30, 60, 300 seconds. Maximum: 600 seconds (10 minutes). RETURNS: { tokenName, slo...
This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-set-slow-mode.md
What gala_launchpad_set_slow_mode does on Gala
AI agents use gala_launchpad_set_slow_mode to create or update resources in Gala, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gala environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tokenName | string | Yes | Token name. |
slowModeSeconds | number | Yes | Slow mode interval in seconds (0 = disabled, max 600). Common values: 0, 10, 30, 60, 300. |
Parameters from the server's own tool schema.
Why gala_launchpad_set_slow_mode is rated Medium
An AI agent can call gala_launchpad_set_slow_mode faster than any human can review: one bad instruction and it creates or modifies resources in Gala by the hundred, each call as confident as the last.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs gala_launchpad_set_slow_mode 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_set_slow_mode, this is the rule to start with:
gala_launchpad_set_slow_mode stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_set_slow_mode call is checked against it from then on.
Questions about gala_launchpad_set_slow_mode
Set slow mode interval for a stream chat. Slow mode throttles users to one message per N seconds. Enforcement is server-side (Redis-backed rate limiting). Setting to 0 disables slow mode. Valid presets: 0 (off), 10, 30, 60, 300 seconds. Maximum: 600 seconds (10 minutes). RETURNS: { tokenName, slowModeSeconds } Authentication: Requires streamAdminApiKey (admin) OR JWT auth (token owner/moderator). It is categorised as a Write tool in the Gala MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
gala_launchpad_set_slow_mode accepts 2 parameters: tokenName, slowModeSeconds. Required: tokenName, slowModeSeconds. 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_set_slow_mode: 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_set_slow_mode is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gala_launchpad_set_slow_mode 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_set_slow_mode. 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_set_slow_mode 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