repair_module
Repair wear on a module using a Repair Kit (Module must be in cargo (not fitted). Consumes 1 repair_kit. Repair amount scales with your relevant skill level. Must be docked at a base with repair service.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/repair-module.md
What repair_module does on SpaceMolt
AI agents use repair_module 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 |
|---|---|---|---|
module_id | string | Yes | Instance ID of the module to repair (must be in cargo, not fitted) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why repair_module is rated Medium
This tool modifies the state of a module (restoring wear/durability) and consumes a resource (repair_kit). It is reversible in the sense that it changes game state in a non-destructive way — it restores something rather than deleting or irreversibly removing it. No financial transaction, no code execution, and no destructive action occurs. Write is the most appropriate category.
From the tool's definition Repair wear on a module using a Repair Kit... Consumes 1 repair_kit. Repair amount scales with your relevant skill level.
Attacks that exploit this kind of access
The rule that runs repair_module 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 repair_module, this is the rule to start with:
repair_module 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 repair_module call is checked against it from then on.
Questions about repair_module
Repair wear on a module using a Repair Kit (Module must be in cargo (not fitted). Consumes 1 repair_kit. Repair amount scales with your relevant skill level. Must be docked at a base with repair service.). 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.
repair_module accepts 2 parameters: module_id, session_id. Required: module_id, 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 repair_module: 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.
repair_module 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 repair_module 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 repair_module. 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.
repair_module 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