wmo-weather.reference.city_search
Search the WMO World Weather Information Service directory of ~2,600 cities by city or country name (case-insensitive partial match). Returns each match's WMO city ID, needed by wmo-weather.forecast and wmo-weather.climate_normals. Example: query="Tokyo" or query="Argentina". Data: worldweather.w...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/wmo-weather.reference.city-search.md
What wmo-weather.reference.city_search does on Apibase
AI agents call wmo-weather.reference.city_search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum number of matching cities to return (default 20, max 50). |
query | string | Yes | City or country name to search for (case-insensitive partial match), e.g. "Tokyo", "Kabul", or "Argentina". Matches against ~2,600 cities in the WMO city direct |
Parameters from the server's own tool schema.
Why wmo-weather.reference.city_search is rated Low
Retrieves public weather reference data without modification or execution capability.
From the tool's definition Search directory, returns city ID, no auth required, no side effects.
Attacks that exploit this kind of access
The rule that runs wmo-weather.reference.city_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wmo-weather.reference.city_search, this is the rule to start with:
wmo-weather.reference.city_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every wmo-weather.reference.city_search call is checked against it from then on.
Questions about wmo-weather.reference.city_search
Search the WMO World Weather Information Service directory of ~2,600 cities by city or country name (case-insensitive partial match). Returns each match's WMO city ID, needed by wmo-weather.forecast and wmo-weather.climate_normals. Example: query="Tokyo" or query="Argentina". Data: worldweather.wmo.int, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
wmo-weather.reference.city_search accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for wmo-weather.reference.city_search: 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 Apibase. Nothing to install.
wmo-weather.reference.city_search 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 wmo-weather.reference.city_search 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 wmo-weather.reference.city_search. 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.
wmo-weather.reference.city_search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue