Convert location names or addresses to coordinates using geocoding.
AI agents call geocode_location to retrieve information from OpenWeatherMap MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a geocoding service to resolve a location string into latitude/longitude coordinates. It retrieves data without creating, modifying, deleting, or executing any external operations. The operation is read-only and produces no side effects on any system or data store.
From the tool's definition Tool converts location names/addresses to coordinates using geocoding—a pure data retrieval operation with no side effects. Description explicitly states it 'converts' (retrieves) without modification or deletion.
Attacks that exploit this kind of access
Convert location names or addresses to coordinates using geocoding. It is categorised as a Read tool in the OpenWeatherMap MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenWeatherMap MCP Server MCP server in PolicyLayer and add a rule for geocode_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 OpenWeatherMap MCP Server. Nothing to install.
geocode_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 geocode_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 geocode_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.
geocode_location is provided by the OpenWeatherMap MCP Server MCP server (tristau/openweathermap-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 →