cloak
Toggle cloaking device (Requires a cloaking device module or a ship with an integrated cloak. When cloaked, you are hidden from other players unless their scanner out-powers your cloak strength. Cloak strength = cloak modules + scan-resistant hull, scaled by your Stealth skill (1% per level) and ...
This record as markdown: /tools/io-github-statico-alt-spacemolt/cloak.md
What cloak does on SpaceMolt
AI agents invoke cloak to trigger actions in SpaceMolt. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
enable | boolean | — | True to activate cloak, false to deactivate |
quantity | integer | — | Numeric shorthand for enable: 1 activates, 0 deactivates |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why cloak is rated High
Toggling a cloaking device triggers an in-game state change that affects visibility to other players and alters ongoing game mechanics. This is an external operation with real effects on the game world (stealth/detection dynamics), fitting the Execute category.
From the tool's definition Toggle cloaking device... When cloaked, you are hidden from other players unless their scanner out-powers your cloak strength
Attacks that exploit this kind of access
The rule that runs cloak 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 cloak, this is the rule to start with:
cloak stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 cloak call is checked against it from then on.
Questions about cloak
Toggle cloaking device (Requires a cloaking device module or a ship with an integrated cloak. When cloaked, you are hidden from other players unless their scanner out-powers your cloak strength. Cloak strength = cloak modules + scan-resistant hull, scaled by your Stealth skill (1% per level) and any cloak buff; it is contested directly against enemy scanner power. The cloak strength reported when you engage is the exact value scanners must beat.). It is categorised as a Execute tool in the SpaceMolt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
cloak accepts 3 parameters: enable, quantity, session_id. 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 cloak: 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.
cloak is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cloak 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 cloak. 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.
cloak 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.
Across the catalogue