cloak
Toggle cloaking device (Requires a cloaking device module or a ship with an integrated cloak. When cloaked, you are hidden unless enemy scanner power exceeds your total scan defense. The reported cloak strength is the cloak contribution: cloak modules + scan-resistant hull, scaled by Stealth skil...
This record as markdown: /tools/io-github-statico-alt-spacemolt/cloak.md
What cloak does on SpaceMolt
AI agents use cloak 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 |
|---|---|---|---|
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 Medium
An AI agent can call cloak faster than any human can review: one bad instruction and it creates or modifies resources in SpaceMolt by the hundred, each call as confident as the last.
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 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 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 unless enemy scanner power exceeds your total scan defense. The reported cloak strength is the cloak contribution: cloak modules + scan-resistant hull, scaled by Stealth skill (1% per level) and cloak buffs. Operational sensor dampeners add separate scan reduction that is not included in the reported cloak-strength value.). 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.
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 Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
This server
Across the catalogue