Get status of your cities including food advantage at founding (indicates growth potential) and current production. Cities with negative food advantage will struggle to grow without improvements like Granaries or Farms.
AI agents call get_city_status 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 returns game state information (city status, food metrics, production data) without side effects. It is a read-only query into game data. The severity is low because misuse by an AI agent would only affect decision-making within the game simulation, not cause harm outside the game or irreversible damage.
From the tool's definition Tool name 'get_city_status' and description explicitly state it 'Get[s] status of your cities' including 'food advantage' and 'current production.' The verbs are retrieval-only: 'Get,' 'indicates.' No creation, modification, deletion, or execution of external…
Attacks that exploit this kind of access
Get status of your cities including food advantage at founding (indicates growth potential) and current production. Cities with negative food advantage will struggle to grow without improvements like Granaries or Farms. 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_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 Civ6mcp. Nothing to install.
get_city_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 get_city_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 get_city_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.
get_city_status 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 →