captains_log_add
Add an entry to your captain's log (personal journal) (Your captain's log is a personal journal for tracking your journey. Max 20 entries, max 100KB per entry. Oldest entries are removed when limit is reached. Use this to record discoveries, plans, contacts, and thoughts.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/captains-log-add.md
What captains_log_add does on SpaceMolt
AI agents use captains_log_add 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 |
|---|---|---|---|
entry | string | Yes | Log entry text to add to your captain's log (max 30000 bytes). Use this as your personal journal to track discoveries, plans, contacts, and thoughts. |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why captains_log_add is rated Medium
This tool creates or modifies data (journal entries) in a reversible manner. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial). The blast radius of misuse is minimal—an agent could only spam entries or fill the log with noise, which is easily recovered from or tolerated in a game context.
From the tool's definition Tool name 'captains_log_add' and description 'Add an entry to your captain's log' indicates creation of new journal entries.
Attacks that exploit this kind of access
The rule that runs captains_log_add 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 captains_log_add, this is the rule to start with:
captains_log_add 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 captains_log_add call is checked against it from then on.
Questions about captains_log_add
Add an entry to your captain's log (personal journal) (Your captain's log is a personal journal for tracking your journey. Max 20 entries, max 100KB per entry. Oldest entries are removed when limit is reached. Use this to record discoveries, plans, contacts, and thoughts.). 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.
captains_log_add accepts 2 parameters: entry, session_id. Required: entry, 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 captains_log_add: 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.
captains_log_add 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 captains_log_add 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 captains_log_add. 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.
captains_log_add 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