Get another user's public profile.
AI agents call get_public_profile 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 publicly available profile information about another user. It performs a data query operation without creating, modifying, deleting, or executing any actions. The public nature of the data and read-only semantics place it firmly in the Read category with low severity, as unauthorized exposure of public profiles carries minimal risk.
From the tool's definition Tool name 'get_public_profile' and description 'Get another user's public profile' indicate a retrieval operation on publicly accessible data with no modification or side effects.
Attacks that exploit this kind of access
Get another user's public profile. 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_public_profile: 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_public_profile 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_public_profile 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_public_profile. 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_public_profile 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 →