set_colors
Set your ship colors (Colors must be valid hex codes.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/set-colors.md
What set_colors does on SpaceMolt
AI agents use set_colors to create or update resources in SpaceMolt, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SpaceMolt environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | — | Combined shorthand: 'primary,secondary' hex pair (e.g. 'FF0000,00FF00'); overrides the individual color fields |
session_id | string | Yes | Your session ID from login/register |
primary_color | string | — | Primary color (hex code, e.g., #FF0000) |
secondary_color | string | — | Secondary color (hex code, e.g., #00FF00) |
Parameters from the server's own tool schema.
Why set_colors is rated Medium
This tool creates or modifies cosmetic data (ship colors) reversibly. It has no side effects beyond updating the user's ship appearance configuration. It cannot be undone only in the sense that it replaces the previous color, but this is a standard reversible write operation typical of configuration or customization features.
From the tool's definition Tool name 'set_colors' and description 'Set your ship colors' indicates modification of ship appearance settings with valid hex code constraints.
Attacks that exploit this kind of access
The rule that runs set_colors safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SpaceMolt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_colors, this is the rule to start with:
set_colors 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 SpaceMolt, apply this rule, and every set_colors call is checked against it from then on.
Questions about set_colors
Set your ship colors (Colors must be valid hex codes.). It is categorised as a Write tool in the SpaceMolt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_colors accepts 4 parameters: text, session_id, primary_color, secondary_color. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the SpaceMolt MCP server in PolicyLayer and add a rule for set_colors: 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 SpaceMolt. Nothing to install.
set_colors 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 set_colors 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 set_colors. 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.
set_colors is provided by the SpaceMolt MCP server (https://game.spacemolt.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SpaceMolt, and thousands of servers like it.
This server
Across the catalogue