List all known API endpoints and their current status.
AI agents call list_available_endpoints 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 performs a simple information retrieval operation that queries and returns metadata about available API endpoints. It has no side effects—it does not modify data, execute commands, delete anything, or trigger financial transactions. The action of 'list' combined with 'check status' are classic Read operations.
From the tool's definition Tool name 'list_available_endpoints' and description 'List all known API endpoints and their current status' indicate retrieval and querying of endpoint metadata without modification or execution.
Attacks that exploit this kind of access
List all known API endpoints and their current 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 list_available_endpoints: 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.
list_available_endpoints 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 list_available_endpoints 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 list_available_endpoints. 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.
list_available_endpoints 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 →