msc-geomet.climate.daily
Get daily climate observations (mean/min/max temperature, precipitation, rain, snow, snow on ground, max wind gust, heating/cooling degree days) for a Canadian station by CLIMATE_IDENTIFIER (from msc-geomet.climate_stations), optionally scoped to a start_date/ end_date range. Data: api.weather.gc...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/msc-geomet.climate.daily.md
What msc-geomet.climate.daily does on Apibase
AI agents call msc-geomet.climate.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 |
|---|---|---|---|
limit | integer | — | Max records to return (1-366). Defaults to 30. |
end_date | string | — | End of the date range, format YYYY-MM-DD. Must be paired with start_date. |
start_date | string | — | Start of the date range, format YYYY-MM-DD. Must be paired with end_date. |
climate_identifier | string | Yes | Station CLIMATE_IDENTIFIER, e.g. "6158731" (Toronto Intl A). Get station IDs from msc-geomet.climate_stations. |
Parameters from the server's own tool schema.
Why msc-geomet.climate.daily is rated Low
Retrieves historical weather data with no side effects or access controls.
From the tool's definition Get daily climate observations for Canadian station, no auth required
Attacks that exploit this kind of access
The rule that runs msc-geomet.climate.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 msc-geomet.climate.daily, this is the rule to start with:
msc-geomet.climate.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 msc-geomet.climate.daily call is checked against it from then on.
Questions about msc-geomet.climate.daily
Get daily climate observations (mean/min/max temperature, precipitation, rain, snow, snow on ground, max wind gust, heating/cooling degree days) for a Canadian station by CLIMATE_IDENTIFIER (from msc-geomet.climate_stations), optionally scoped to a start_date/ end_date range. Data: api.weather.gc.ca (MSC GeoMet OGC API - Features), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
msc-geomet.climate.daily accepts 4 parameters: limit, end_date, start_date, climate_identifier. Required: climate_identifier. 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 msc-geomet.climate.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.
msc-geomet.climate.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 msc-geomet.climate.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 msc-geomet.climate.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.
msc-geomet.climate.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