Get Battle Royale game details.
AI agents call get_battle_royale 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 retrieves game details from the GeoGuessr API without modifying, executing, deleting, or creating any data. It is a standard read operation that would be used to fetch information about Battle Royale games for analysis purposes, consistent with the server's stated purpose of game statistics and performance tracking.
From the tool's definition Tool name 'get_battle_royale' with description 'Get Battle Royale game details' indicates a retrieval operation. The verb 'Get' and the context of analyzing game statistics on a GeoGuessr MCP server confirm this is a read-only query with no side effects.
Attacks that exploit this kind of access
Get Battle Royale game details. 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_battle_royale: 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_battle_royale 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_battle_royale 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_battle_royale. 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_battle_royale 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 →