AI agents call get_city_production to retrieve information from Civ6mcp 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 current production status of cities in a Civilization VI game. It has no side effects; it only reads and reports existing game data. While the data retrieved (e.g., military units, advanced projects) could be strategically sensitive within the game context, the tool itself performs only a read operation.
From the tool's definition Tool name is 'get_city_production' and description states 'Get what every city is currently building' — a retrieval operation with no modification, creation, or deletion of game state.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get what every city is currently building, including strategic items like Giant Death Robots, Manhattan Project, and space race projects. It is categorised as a Read tool in the Civ6mcp MCP Server, which means it retrieves data without modifying state.
Register the Civ6 MCP server in PolicyLayer and add a rule for get_city_production: 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 Civ6mcp. Nothing to install.
get_city_production 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 get_city_production 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 get_city_production. 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.
get_city_production is provided by the Civ6 MCP server (lowrykun/civ6mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →