Get location information using current IP address via ipify and ipinfo
AI agents call get-my-location to retrieve information from Mylocation without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries external location services and returns data without any side effects. It performs a read-only operation that retrieves geographic information associated with an IP address. No data is created, modified, deleted, or executed. The information returned could be considered sensitive (user's approximate location), but that is a data sensitivity issue rather than a capability classification issue.
From the tool's definition Tool retrieves location information based on current IP address using ipify and ipinfo services. Description uses 'get' and retrieval language with no mention of modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Get location information using current IP address via ipify and ipinfo. It is categorised as a Read tool in the Mylocation MCP Server, which means it retrieves data without modifying state.
Register the Mylocation MCP server in PolicyLayer and add a rule for get-my-location: 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 Mylocation. Nothing to install.
get-my-location 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-my-location 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-my-location. 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-my-location is provided by the Mylocation MCP server (yhwancha/mylocation-mcp). 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 →