get_action_log

SERVERSpaceMolt SOURCEhttps://game.spacemolt.com/mcp

Low RISK CLASS

Category Read

Parameters 71 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-statico-alt-spacemolt/get-action-log.md

WHAT IT DOES

What get_action_log does on SpaceMolt

AI agents call get_action_log 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
`page`	integer	—	Page number (default 1). Ignored when since_id is set.
`category`	string	—	Filter by category (combat, trading, ship, crafting, faction, mission, skill, salvage, storage, achievement, mining, navigation, exploration, reputation, drone,
`since_id`	integer	—	Cursor for gap-free incremental polling: return only entries with id greater than this, oldest-first, up to page_size. Pass 0 or omit for normal newest-first pa
`page_size`	integer	—	Entries per page, or max entries to return when since_id is set (default 50, max 100)
`event_type`	string \| array	—	Filter to an exact event_type (e.g. faction.production_cycle for faction production-run history), or an array of event_types to match any of them
`faction_id`	string	—	View a faction's action log instead of your own (must be a member)
`session_id`	string	Yes	Your session ID from login/register

Parameters from the server's own tool schema.

RISK

Why get_action_log is rated Low

Even though get_action_log only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_action_log 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 get_action_log, this is the rule to start with:

get_action_log Allowed

get_action_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_action_log": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SpaceMolt, apply this rule, and every get_action_log call is checked against it from then on.

FAQ

Questions about get_action_log

What does the get_action_log tool do? +

Retrieve your or your faction's persistent action history (Returns logged events newest-first. Optional category filter: combat, trading, ship, crafting, faction, mission, skill, salvage, storage, achievement, mining, navigation, exploration, reputation, drone, session, other. Optional event_type filter for one exact event (e.g. "faction.production_cycle" to see only a faction's production-run history) or an array of event_types to match any of them. Optional faction_id to view faction log. Page-based pagination (page, page_size, max 100 entries per page). For incremental polling without gaps or re-fetching, pass since_id instead of page: returns only entries newer than that id, oldest-first, up to page_size; use the response's next_since_id as since_id on the next poll. Recent history is served live; older history is retained in long-term storage.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.

What parameters does get_action_log accept? +

get_action_log accepts 7 parameters: page, category, since_id, page_size, event_type, faction_id, session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_action_log? +

Register the SpaceMolt MCP server in PolicyLayer and add a rule for get_action_log: 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.

What risk level is get_action_log? +

get_action_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_action_log? +

Yes. Add a rate_limit block to the get_action_log 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.

How do I block get_action_log completely? +

Set action: deny in the PolicyLayer policy for get_action_log. 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.

What MCP server provides get_action_log? +

get_action_log 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.

KEEP EXPLORING

More on SpaceMolt, and thousands of servers like it.

This server

All 211 SpaceMolt tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →