ncei.climate.daily_data
Retrieve historical daily weather observations from NOAA NCEI — max/min temperature, precipitation, snowfall, wind speed. 260+ years of records from global stations. Values in tenths of °C (temp) and tenths of mm (precip). Source: GHCND dataset.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ncei.climate.daily-data.md
What ncei.climate.daily_data does on Apibase
AI agents call ncei.climate.daily_data 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 date in YYYY-MM-DD format (e.g. 2025-01-31). Max 1 year range. |
datatypes | string | — | Comma-separated data types: TMAX (max temp), TMIN (min temp), PRCP (precipitation), SNOW, AWND (avg wind). Default: all. |
start_date | string | Yes | Start date in YYYY-MM-DD format (e.g. 2025-01-01) |
station_id | string | Yes | NCEI station ID (e.g. GHCND:USW00094728 for Central Park, NY). Get from ncei.stations tool. |
Parameters from the server's own tool schema.
Why ncei.climate.daily_data is rated Low
Tool only queries historical weather data with no side effects or ability to modify external systems.
From the tool's definition Retrieve historical daily weather observations; no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs ncei.climate.daily_data 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 ncei.climate.daily_data, this is the rule to start with:
ncei.climate.daily_data 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 ncei.climate.daily_data call is checked against it from then on.
Questions about ncei.climate.daily_data
Retrieve historical daily weather observations from NOAA NCEI — max/min temperature, precipitation, snowfall, wind speed. 260+ years of records from global stations. Values in tenths of °C (temp) and tenths of mm (precip). Source: GHCND dataset. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ncei.climate.daily_data accepts 4 parameters: end_date, datatypes, 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 ncei.climate.daily_data: 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.
ncei.climate.daily_data 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 ncei.climate.daily_data 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 ncei.climate.daily_data. 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.
ncei.climate.daily_data 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