uninstall_mod
Uninstall a module from your ship (module_id accepts a module instance ID (from get_ship) or a module type ID (e.g. 'pulse_laser_i'). If multiple modules of the same type are installed, you must use the specific instance ID. Module is returned to your cargo.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/uninstall-mod.md
What uninstall_mod does on SpaceMolt
AI agents use uninstall_mod 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 | Module ID to install/uninstall. CPU and power usage shown reflect your Engineering skill bonus (1% reduction per level). |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why uninstall_mod is rated Medium
The action removes a module from the ship and places it in cargo — it is reversible (the module is not destroyed, just relocated). This is a Write operation (modifies ship configuration), not Destructive. Misuse could disrupt ship capabilities mid-combat or exploration, hence medium severity.
From the tool's definition Uninstall a module from your ship...Module is returned to your cargo
Attacks that exploit this kind of access
The rule that runs uninstall_mod 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 uninstall_mod, this is the rule to start with:
uninstall_mod 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 uninstall_mod call is checked against it from then on.
Questions about uninstall_mod
Uninstall a module from your ship (module_id accepts a module instance ID (from get_ship) or a module type ID (e.g. 'pulse_laser_i'). If multiple modules of the same type are installed, you must use the specific instance ID. Module is returned to your cargo.). 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.
uninstall_mod 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 uninstall_mod: 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.
uninstall_mod 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 uninstall_mod 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 uninstall_mod. 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.
uninstall_mod 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