install_mod
Install a module on your ship (Module must be in your cargo. Requires CPU/power grid capacity. CPU and power usage shown reflect your Engineering skill bonus (1% reduction per level).)
This record as markdown: /tools/io-github-statico-alt-spacemolt/install-mod.md
What install_mod does on SpaceMolt
AI agents use install_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 install_mod is rated Medium
Installing a module modifies the player's ship configuration but does not execute arbitrary code or trigger external systems. The action is reversible (modules can presumably be uninstalled). While it affects game state, the blast radius is limited to the player's own ship loadout and does not permit data deletion or irreversible destruction.
From the tool's definition Tool performs 'install' action which modifies ship state by adding a module. Description indicates it changes ship configuration, CPU allocation, and power grid status - all reversible modifications to game entity properties.
Attacks that exploit this kind of access
The rule that runs install_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 install_mod, this is the rule to start with:
install_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 install_mod call is checked against it from then on.
Questions about install_mod
Install a module on your ship (Module must be in your cargo. Requires CPU/power grid capacity. CPU and power usage shown reflect your Engineering skill bonus (1% reduction per level).). 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.
install_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 install_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.
install_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 install_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 install_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.
install_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