analyze_recent_games
AI agents call analyze_recent_games to retrieve information from GeoGuessr MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to analyze historical game data for the user, which is a non-destructive read operation. No side effects, modifications, deletions, code execution, or financial transactions are implied. The empty description prevents higher confidence, but the naming convention and server context strongly suggest this retrieves and processes existing game statistics rather than modifying or executing operations.
From the tool's definition Tool name 'analyze_recent_games' combined with server description indicating 'analysis of GeoGuessr game statistics' and 'performance tracking' suggests data retrieval and analysis operations.
Attacks that exploit this kind of access
analyze_recent_games. It is categorised as a Read tool in the GeoGuessr MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GeoGuessr MCP Server MCP server in PolicyLayer and add a rule for analyze_recent_games: 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 GeoGuessr MCP Server. Nothing to install.
analyze_recent_games 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 analyze_recent_games 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 analyze_recent_games. 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.
analyze_recent_games is provided by the GeoGuessr MCP Server MCP server (nyxiumyuuki/geoguessrmcp). 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 →