Search for locations using OpenStreetMap Nominatim API.
AI agents call search_location to retrieve information from MCP Weather SSE 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 read-only search against a public geocoding API (Nominatim). It retrieves location information based on user input but has no side effects, does not execute code, does not modify data, and does not involve financial transactions. The low severity reflects minimal risk even if misused, as it only returns publicly available geographic information.
From the tool's definition Tool name 'search_location' and description 'Search for locations using OpenStreetMap Nominatim API' indicate a query operation that retrieves location data without modifying or deleting anything.
Attacks that exploit this kind of access
Search for locations using OpenStreetMap Nominatim API. It is categorised as a Read tool in the MCP Weather SSE Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Weather SSE Server MCP server in PolicyLayer and add a rule for search_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 MCP Weather SSE Server. Nothing to install.
search_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 search_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 search_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.
search_location is provided by the MCP Weather SSE Server MCP server (tranducthai/mcp_protocol_for_llm). 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 →