search_locations

Search for cities and towns by partial name or postcode. Returns an array of matching locations with their coordinates, region, country, and URL slug. Useful for building location pickers or resolving ambiguous place names.

Server WeatherAPI MCP Server weatherapicom/weatherapi-mcp
Category Read
Risk class Low
Parameters 00 required

What search_locations does on WeatherAPI MCP Server

AI agents call search_locations to retrieve information from WeatherAPI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why search_locations needs a policy

This tool retrieves location data based on search criteria (partial name or postcode) and returns results. It has no capability to modify data, execute code, delete records, or commit financial transactions. The operation is idempotent and read-only, making it a standard Read category tool with low severity risk.

From the tool's definition Tool 'search_locations' performs a search query that 'Returns an array of matching locations' — a pure retrieval operation with no side effects.

Questions about search_locations

What does the search_locations tool do? +

Search for cities and towns by partial name or postcode. Returns an array of matching locations with their coordinates, region, country, and URL slug. Useful for building location pickers or resolving ambiguous place names. It is categorised as a Read tool in the WeatherAPI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_locations? +

Register the WeatherAPI MCP Server MCP server in PolicyLayer and add a rule for search_locations: 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 WeatherAPI MCP Server. Nothing to install.

What risk level is search_locations? +

search_locations is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_locations? +

Yes. Add a rate_limit block to the search_locations 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.

How do I block search_locations completely? +

Set action: deny in the PolicyLayer policy for search_locations. 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.

What MCP server provides search_locations? +

search_locations is provided by the WeatherAPI MCP Server MCP server (weatherapicom/weatherapi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.