check_api_status
AI agents call check_api_status 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 name 'check_api_status' indicates a query operation that retrieves the current status of an API endpoint. Given the server's stated feature of 'automatic API monitoring', this is clearly a Read operation that fetches status data. The empty description lowers confidence slightly, but the naming and context strongly suggest a non-destructive information retrieval function with no side effects.
From the tool's definition Tool named 'check_api_status' with no description provided. Based on naming convention and context within a monitoring/analysis server ('automatic API monitoring' mentioned in server description), this tool retrieves API status information without modifying…
Attacks that exploit this kind of access
check_api_status. 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 check_api_status: 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.
check_api_status 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 check_api_status 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 check_api_status. 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.
check_api_status 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 →