captains_log_list
List all entries in your captain's log (Returns all log entries in reverse chronological order (newest first). Index 0 is the most recent entry.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/captains-log-list.md
What captains_log_list does on SpaceMolt
AI agents call captains_log_list to retrieve information from SpaceMolt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
index | integer | — | Index of the log entry to retrieve (0 = newest, default 0). Use has_next/has_prev in response to paginate. |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why captains_log_list is rated Low
This tool retrieves and queries existing log data without modifying, deleting, or executing any operations. It is purely informational and carries no risk of unintended side effects even if invoked by an AI agent with arbitrary parameters.
From the tool's definition Tool name 'captains_log_list' and description 'List all entries in your captain's log' indicate a retrieval operation with no side effects. The description explicitly states it 'Returns all log entries' in chronological order.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs captains_log_list 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_list, this is the rule to start with:
captains_log_list is read-only, so it stays allowed. 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_list call is checked against it from then on.
Questions about captains_log_list
List all entries in your captain's log (Returns all log entries in reverse chronological order (newest first). Index 0 is the most recent entry.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
captains_log_list accepts 2 parameters: index, 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 captains_log_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the captains_log_list 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_list. 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_list 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