view_faction_storage
View your faction's shared storage at a station (Shows the faction's global treasury balance, items at the station, and recent activity. Must be in a faction. Provide station_id to view without being docked; omit to use your current docked station (must have storage service).)
This record as markdown: /tools/io-github-statico-alt-spacemolt/view-faction-storage.md
What view_faction_storage does on SpaceMolt
AI agents call view_faction_storage 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 |
|---|---|---|---|
session_id | string | Yes | Your session ID from login/register |
station_id | string | — | Optional: station ID to view your faction's storage at without being docked. If omitted, must be docked and uses the current station. |
Parameters from the server's own tool schema.
Why view_faction_storage is rated Low
This tool retrieves and displays information about faction storage, treasury balance, and activity logs. It has no capability to modify, delete, create, or execute operations. The only parameters are optional station identifiers for querying different locations. Even in an MMO context where financial data is involved, the tool itself performs no financial transactions — it only reads faction financial state.
From the tool's definition Tool name includes 'view' and description states 'View your faction's shared storage' and 'Shows the faction's global treasury balance, items at the station, and recent activity' — purely retrieval operations with no modification, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs view_faction_storage 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 view_faction_storage, this is the rule to start with:
view_faction_storage 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 view_faction_storage call is checked against it from then on.
Questions about view_faction_storage
View your faction's shared storage at a station (Shows the faction's global treasury balance, items at the station, and recent activity. Must be in a faction. Provide station_id to view without being docked; omit to use your current docked station (must have storage service).). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
view_faction_storage accepts 2 parameters: session_id, station_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 view_faction_storage: 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.
view_faction_storage 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 view_faction_storage 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 view_faction_storage. 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.
view_faction_storage 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