Get current session state and instructions. Call this FIRST to understand what
AI agents call session_status to retrieve information from Factorio AI Companion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves session metadata without modifying, executing operations on, or deleting data. It is a read-only information retrieval operation, representing minimal risk if misused by an AI agent. The low severity reflects that session state information alone cannot directly harm the game or system.
From the tool's definition Tool name is 'session_status' and description indicates it 'Get[s] current session state and instructions' — retrieves state information with no side effects.
Documented attack patterns abuse exactly the kind of access session_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Factorio AI Companion, and nothing reaches the server without passing your rules. This is the rule we recommend for session_status:
{
"version": "1",
"default": "deny",
"tools": {
"session_status": {}
}
}session_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get current session state and instructions. Call this FIRST to understand what. It is categorised as a Read tool in the Factorio AI Companion MCP Server, which means it retrieves data without modifying state.
Register the Factorio AI Companion MCP server in PolicyLayer and add a rule for session_status: 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 Factorio AI Companion. Nothing to install.
session_status 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 session_status 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 session_status. 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.
session_status is provided by the Factorio AI Companion MCP server (lveillard/factorio-ai-companion). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Factorio AI Companion, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Factorio AI Companion tools catalogued and risk-classified — across an index of 43,000+ MCP servers.