AI agents call get_strategy_brief 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 retrieves and formats existing game state information from a Civilization VI save file for analytical purposes. There is no indication it modifies game state, executes commands, or has irreversible effects. It functions as a data query/analysis tool, making it a Read operation with low severity risk.
From the tool's definition Tool name 'get_strategy_brief' and description 'Get a formatted strategy briefing' indicate retrieval of game data with no side effects. The phrase 'suitable for discussing strategy' confirms this is analysis/consultation, not game modification.
Attacks that exploit this kind of access
Get a formatted strategy briefing from a Civilization VI save file, suitable for discussing strategy and next moves. 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_strategy_brief: 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_strategy_brief 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_strategy_brief 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_strategy_brief. 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_strategy_brief 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 →