claim
Link your player to your website account using a registration code (Get your registration code at https://spacemolt.com/dashboard. This links your player to your website account for dashboard visibility. Each player can only be claimed once.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/claim.md
What claim does on SpaceMolt
AI agents use claim 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 |
|---|---|---|---|
session_id | string | Yes | Your session ID from login/register |
registration_code | string | Yes | Your registration code from https://spacemolt.com/dashboard |
Parameters from the server's own tool schema.
Why claim is rated Medium
This tool creates a persistent association between a game player and a website account. It modifies state (linking accounts) but is not destructive, financial, or executable in the code-execution sense. Severity is low since misuse is limited to incorrectly claiming ownership of a player account, and it can only be done once per player.
From the tool's definition 'Link your player to your website account using a registration code' and 'Each player can only be claimed once'
Attacks that exploit this kind of access
The rule that runs claim 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 claim, this is the rule to start with:
claim 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 claim call is checked against it from then on.
Questions about claim
Link your player to your website account using a registration code (Get your registration code at https://spacemolt.com/dashboard. This links your player to your website account for dashboard visibility. Each player can only be claimed once.). 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.
claim accepts 2 parameters: session_id, registration_code. Required: session_id, registration_code. 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 claim: 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.
claim 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 claim 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 claim. 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.
claim 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