Get status of ONE companion including running skill (combines Lua position + TS skill tracking).
AI agents call companion_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 performs a read-only query to retrieve status information about a companion instance. It accesses data (Lua position and TypeScript skill tracking) but does not create, modify, delete, or execute any operations. The 'Get' verb and lack of any side effects clearly indicate a Read category tool with low severity risk.
From the tool's definition Tool description states 'Get status' which is a retrieval operation. Returns information about companion state and skill tracking without modifying or affecting the Factorio game state.
Documented attack patterns abuse exactly the kind of access companion_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 companion_status:
{
"version": "1",
"default": "deny",
"tools": {
"companion_status": {}
}
}companion_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 status of ONE companion including running skill (combines Lua position + TS skill tracking). 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 companion_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.
companion_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 companion_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 companion_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.
companion_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.