meteostat.stations.nearby
Find Meteostat weather stations near a latitude/longitude coordinate, sorted by distance. Returns station IDs to use with station_info and the daily/monthly/hourly observation tools. Data: Meteostat open station directory (CC BY 4.0), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/meteostat.stations.nearby.md
What meteostat.stations.nearby does on Apibase
AI agents call meteostat.stations.nearby 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 |
|---|---|---|---|
lat | number | Yes | Latitude of the search point (WGS84 decimal degrees). |
lon | number | Yes | Longitude of the search point (WGS84 decimal degrees). |
limit | integer | — | Maximum number of stations to return, nearest first (default 10, max 50). |
radius_km | number | — | Search radius in kilometers (default 100, max 500). |
Parameters from the server's own tool schema.
Why meteostat.stations.nearby is rated Low
Retrieves meteorological station metadata from public open data; no modification, execution, or side effects.
From the tool's definition Find weather stations near coordinates, returns station IDs, public data
Attacks that exploit this kind of access
The rule that runs meteostat.stations.nearby 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 meteostat.stations.nearby, this is the rule to start with:
meteostat.stations.nearby 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 meteostat.stations.nearby call is checked against it from then on.
Questions about meteostat.stations.nearby
Find Meteostat weather stations near a latitude/longitude coordinate, sorted by distance. Returns station IDs to use with station_info and the daily/monthly/hourly observation tools. Data: Meteostat open station directory (CC BY 4.0), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
meteostat.stations.nearby accepts 4 parameters: lat, lon, limit, radius_km. Required: lat, lon. 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 meteostat.stations.nearby: 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.
meteostat.stations.nearby 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 meteostat.stations.nearby 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 meteostat.stations.nearby. 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.
meteostat.stations.nearby 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