meteostat.observations.daily
Get a full calendar year of daily weather observations (temperature, precipitation, wind, pressure, sunshine, cloud cover) for a Meteostat weather station. Station ID comes from meteostat.stations_nearby. Data: Meteostat, aggregated from national weather services (CC BY 4.0), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/meteostat.observations.daily.md
What meteostat.observations.daily does on Apibase
AI agents call meteostat.observations.daily 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 |
|---|---|---|---|
year | integer | Yes | Calendar year to fetch daily observations for (e.g. 2024). |
station_id | string | Yes | Meteostat weather station ID, obtained from meteostat.stations_nearby. |
Parameters from the server's own tool schema.
Why meteostat.observations.daily is rated Low
Tool retrieves historical weather data without side effects, authentication, or access to sensitive information.
From the tool's definition Get a full calendar year of daily weather observations; no auth required
Attacks that exploit this kind of access
The rule that runs meteostat.observations.daily 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.observations.daily, this is the rule to start with:
meteostat.observations.daily 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.observations.daily call is checked against it from then on.
Questions about meteostat.observations.daily
Get a full calendar year of daily weather observations (temperature, precipitation, wind, pressure, sunshine, cloud cover) for a Meteostat weather station. Station ID comes from meteostat.stations_nearby. Data: Meteostat, aggregated from national weather services (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.observations.daily accepts 2 parameters: year, station_id. Required: year, 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.observations.daily: 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.observations.daily 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.observations.daily 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.observations.daily. 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.observations.daily 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