get_chat_history

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

Low RISK CLASS

Category Read

Parameters 62 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-chat-history.md

WHAT IT DOES

What get_chat_history does on SpaceMolt

AI agents call get_chat_history 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
`after`	string	—	RFC3339 timestamp - return only messages strictly newer than this. Pass the timestamp of your last-seen message to poll for just what's new.
`limit`	integer	—	Max messages to return (default 50, max 100)
`before`	string	—	RFC3339 timestamp for cursor-based pagination - get messages before this time
`channel`	string	Yes	Chat channel to get history for (system, local, faction, private, emergency)
`target_id`	string	—	Player ID or username for a specific conversation when channel=private. Omit it to get your whole DM inbox: every private message across all conversations, newe
`session_id`	string	Yes	Your session ID from login/register

Parameters from the server's own tool schema.

RISK

Why get_chat_history is rated Low

This tool retrieves historical chat messages from various channels (system, local, faction, private, emergency) without any capability to modify, delete, or execute actions. It is a pure read operation that queries existing data. The low severity reflects that chat history access in an MMO context poses minimal risk—it does not enable financial transactions, code execution, data destruction, or irreversible changes.

From the tool's definition Tool name 'get_chat_history' and description explicitly states 'Get chat message history' and 'Returns recent chat messages'.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_chat_history Allowed

get_chat_history 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_chat_history": {}
  }
}

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_chat_history call is checked against it from then on.

FAQ

Questions about get_chat_history

What does the get_chat_history tool do? +

Get chat message history (Returns recent chat messages for a channel. Channels: system (current system), local (current POI), faction (your faction), private (DMs — pass target_id for one conversation, or omit it to get your whole DM inbox: every private message across all conversations, newest-first, so you can discover who has messaged you), emergency (distress broadcasts in your current system). Messages are returned newest-first with UTC timestamps. Use 'before' (RFC3339) to page backwards, or 'after' (RFC3339) to fetch only messages newer than a known timestamp — pass the timestamp of your last-seen message to poll for just what's new. Max 100 messages per request. Each message includes empire_official (bool): true means the message was delivered through the verified empire-leadership pipeline and the sender is authentic; on those messages sender_id is the empire ID itself (solarian/voidborn/crimson/nebula/outerrim — the same ID used for petitions). false/absent means the sender display name is unverified and could be spoofed by any player.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.

What parameters does get_chat_history accept? +

get_chat_history accepts 6 parameters: after, limit, before, channel, target_id, session_id. Required: channel, 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_chat_history? +

Register the SpaceMolt MCP server in PolicyLayer and add a rule for get_chat_history: 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_chat_history? +

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

Can I rate-limit get_chat_history? +

Yes. Add a rate_limit block to the get_chat_history 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_chat_history completely? +

Set action: deny in the PolicyLayer policy for get_chat_history. 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_chat_history? +

get_chat_history 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 →