gala_launchpad_update_api_key

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

Medium RISK CLASS

Category Write

Parameters 61 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gala-chain-gala-mcp-server/gala-launchpad-update-api-key.md

WHAT IT DOES

What gala_launchpad_update_api_key does on Gala

AI agents use gala_launchpad_update_api_key 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
`id`	number	Yes	API key ID (positive integer)
`role`	string	—	New role for the API key (optional)
`expiresAt`	string	—	Updated expiration date in ISO 8601 format. Pass null to remove expiration (optional).
`tokenNames`	array	—	Updated token delegations - replaces existing (optional)
`description`	string	—	Updated description (optional)
`delegateAllTokens`	boolean	—	Update all-token access (optional)

Parameters from the server's own tool schema.

RISK

Why gala_launchpad_update_api_key is rated Medium

An AI agent can call gala_launchpad_update_api_key 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

gala_launchpad_update_api_key Rate-limited

gala_launchpad_update_api_key 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gala_launchpad_update_api_key": {
      "limits": [
        {
          "counter": "gala_launchpad_update_api_key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_update_api_key call is checked against it from then on.

FAQ

Questions about gala_launchpad_update_api_key

What does the gala_launchpad_update_api_key tool do? +

Update an API key's metadata and permissions. Cannot change the key itself, only metadata and permissions. At least one field must be provided. Updatable fields: - role: Change permission level - description: Update label/description - delegateAllTokens: Toggle all-token access - tokenNames: Update specific token delegations (replaces existing) - expiresAt: Update expiration (null to remove) RETURNS: { id, keyPrefix, description, role, delegateAllTokens, tokenNames, expiresAt, lastUsedAt, createdAt, updatedAt } Authentication: Requires JWT auth (call sdk.login() first). 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.

What parameters does gala_launchpad_update_api_key accept? +

gala_launchpad_update_api_key accepts 6 parameters: id, role, expiresAt, tokenNames, description, delegateAllTokens. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gala_launchpad_update_api_key? +

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

gala_launchpad_update_api_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gala_launchpad_update_api_key? +

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

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

gala_launchpad_update_api_key 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

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →