set_status
Set your status message and clan tag (Status max 64 chars, clan tag max 4 chars.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/set-status.md
What set_status does on SpaceMolt
AI agents use set_status 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 |
|---|---|---|---|
clan_tag | string | — | Clan tag (max 4 chars) |
session_id | string | Yes | Your session ID from login/register |
status_message | string | — | Status message |
Parameters from the server's own tool schema.
Why set_status is rated Medium
This tool creates or modifies user-facing metadata (status message and clan tag) in the game, which is a Write category action. The severity is low because: (1) changes are cosmetic/social in nature with no impact on game mechanics, inventory, or resources; (2) modifications are entirely reversible—the player can change their status and clan tag again at any time; (3) no financial, destructive, or executable…
From the tool's definition Tool description states it sets user status message and clan tag with character limits (64 chars for status, 4 chars for clan tag). The verb 'set' and the action of modifying profile metadata indicates a reversible write operation.
Attacks that exploit this kind of access
The rule that runs set_status 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_status, this is the rule to start with:
set_status 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_status call is checked against it from then on.
Questions about set_status
Set your status message and clan tag (Status max 64 chars, clan tag max 4 chars.). 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_status accepts 3 parameters: clan_tag, session_id, status_message. 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_status: 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_status 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_status 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_status. 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_status 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