AI agents call get_game_context 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 game state data without creating, modifying, deleting, or executing operations. It is a passive data retrieval function typical of informational MCP servers. The low severity reflects that misuse would only expose in-game information already accessible within the game client, with no ability to alter game state or trigger external effects.
From the tool's definition Tool name 'get_game_context' and description 'Retrieve the stored game context information' indicate a retrieval operation with no modification capability. The verb 'Retrieve' and context of sibling tools (all 'get_*' functions) confirm read-only behavior.
Attacks that exploit this kind of access
Retrieve the stored game context information. 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_game_context: 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_game_context 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_game_context 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_game_context. 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_game_context 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 →