AI agents call get_trend_analysis 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.
The tool retrieves and analyzes game state information for strategic analysis purposes without modifying any game data, executing commands, or causing side effects. It falls squarely into the Read category (retrieve/query data). The low severity reflects that misuse would only expose game information visible to the player, with no destructive, financial, or code execution implications.
From the tool's definition Tool name 'get_trend_analysis' and description indicate it analyzes and retrieves historical trend data ('trends over multiple turns') from the game state. The verb 'analyze' in this context means to examine existing data, not modify or execute operations.
Attacks that exploit this kind of access
Analyze trends over multiple turns showing how each civilization\. 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_trend_analysis: 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_trend_analysis 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_trend_analysis 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_trend_analysis. 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_trend_analysis 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 →