Get current competitive season statistics.
AI agents call get_season_stats 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.
This tool fetches statistical data about a competitive season without creating, modifying, deleting, or executing any operations. It is purely informational and retrievals operations present no direct security risk unless the data itself is extremely sensitive (which season stats in a gaming context are not). Severity is low because misuse would only expose non-sensitive competitive statistics.
From the tool's definition Tool is named 'get_season_stats' and described as retrieving 'current competitive season statistics' — a read-only query operation with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Get current competitive season statistics. 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 get_season_stats: 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.
get_season_stats 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_season_stats 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_season_stats. 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_season_stats 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 →