meteostat.observations.hourly
Get hourly weather observations (temperature, humidity, precipitation, wind, pressure, cloud cover, weather condition code) for a Meteostat weather station over a date range of up to 7 days within a single calendar year. Station ID comes from meteostat.stations_nearby. Use meteostat.daily_data fo...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/meteostat.observations.hourly.md
What meteostat.observations.hourly does on Apibase
AI agents call meteostat.observations.hourly 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 |
|---|---|---|---|
end_date | string | Yes | End of the date range in YYYY-MM-DD format (inclusive). Must be within 7 days of start_date and in the same calendar year — use meteostat.daily_data for longer |
start_date | string | Yes | Start of the date range in YYYY-MM-DD format (inclusive). |
station_id | string | Yes | Meteostat weather station ID, obtained from meteostat.stations_nearby. |
Parameters from the server's own tool schema.
Why meteostat.observations.hourly is rated Low
Retrieves historical weather data with no side effects or capability to modify external systems.
From the tool's definition Get hourly weather observations for a weather station over a date range
Attacks that exploit this kind of access
The rule that runs meteostat.observations.hourly 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.hourly, this is the rule to start with:
meteostat.observations.hourly 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.hourly call is checked against it from then on.
Questions about meteostat.observations.hourly
Get hourly weather observations (temperature, humidity, precipitation, wind, pressure, cloud cover, weather condition code) for a Meteostat weather station over a date range of up to 7 days within a single calendar year. Station ID comes from meteostat.stations_nearby. Use meteostat.daily_data for longer time spans. 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.observations.hourly accepts 3 parameters: end_date, start_date, station_id. Required: end_date, start_date, 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.hourly: 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.hourly 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.hourly 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.hourly. 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.hourly 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