meteostat.observations.monthly
Get the full monthly weather history (mean/min/max temperature, precipitation, pressure, sunshine) for a Meteostat weather station — can span many decades for long-running stations. 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.observations.monthly.md
What meteostat.observations.monthly does on Apibase
AI agents call meteostat.observations.monthly 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, obtained from meteostat.stations_nearby. Returns the full monthly history available for the station (may span decades). |
Parameters from the server's own tool schema.
Why meteostat.observations.monthly is rated Low
Retrieves historical weather data with no side effects or modification capabilities.
From the tool's definition Get the full monthly weather history, no auth required
Attacks that exploit this kind of access
The rule that runs meteostat.observations.monthly 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.monthly, this is the rule to start with:
meteostat.observations.monthly 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.monthly call is checked against it from then on.
Questions about meteostat.observations.monthly
Get the full monthly weather history (mean/min/max temperature, precipitation, pressure, sunshine) for a Meteostat weather station — can span many decades for long-running stations. 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.observations.monthly 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.observations.monthly: 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.monthly 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.monthly 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.monthly. 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.monthly 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