meteostat.stations.info
Get metadata for a Meteostat weather station by ID: name, country/region, coordinates, timezone, and the date ranges of available hourly/daily/monthly data. Station ID comes from meteostat.stations_nearby. Data: Meteostat (CC BY 4.0), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/meteostat.stations.info.md
What meteostat.stations.info does on Apibase
AI agents call meteostat.stations.info 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 |
|---|---|---|---|
station_id | string | Yes | Meteostat weather station ID (e.g. "10637" for Frankfurt Airport), obtained from meteostat.stations_nearby. |
Parameters from the server's own tool schema.
Why meteostat.stations.info is rated Low
Retrieves weather station metadata without side effects, authentication, or sensitive operations.
From the tool's definition Get metadata for a Meteostat weather station by ID: name, country/region, coordinates, timezone
Attacks that exploit this kind of access
The rule that runs meteostat.stations.info 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.info, this is the rule to start with:
meteostat.stations.info 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.info call is checked against it from then on.
Questions about meteostat.stations.info
Get metadata for a Meteostat weather station by ID: name, country/region, coordinates, timezone, and the date ranges of available hourly/daily/monthly data. Station ID comes from meteostat.stations_nearby. Data: Meteostat (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.info accepts 1 parameter: station_id. Required: station_id. 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.info: 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.info 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.info 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.info. 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.info 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