ncei.climate.stations
Search 100K+ global weather stations from NOAA NCEI by location (state FIPS, ZIP, country). Returns station ID, name, coordinates, elevation, and data coverage dates (some from 1700s). Use station IDs with ncei.daily_data for historical climate records.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ncei.climate.stations.md
What ncei.climate.stations does on Apibase
AI agents call ncei.climate.stations 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 | — | Number of stations to return (1-25, default 10) |
location_id | string | Yes | Location ID: FIPS:06 (California), FIPS:36 (New York), ZIP:10001, CITY:US360019, or CNTRY:US |
Parameters from the server's own tool schema.
Why ncei.climate.stations is rated Low
Tool queries and retrieves historical climate data with no modification or side effects.
From the tool's definition Search weather stations, returns station ID, name, coordinates, elevation, data coverage dates.
Attacks that exploit this kind of access
The rule that runs ncei.climate.stations 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.stations, this is the rule to start with:
ncei.climate.stations 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.stations call is checked against it from then on.
Questions about ncei.climate.stations
Search 100K+ global weather stations from NOAA NCEI by location (state FIPS, ZIP, country). Returns station ID, name, coordinates, elevation, and data coverage dates (some from 1700s). Use station IDs with ncei.daily_data for historical climate records. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ncei.climate.stations accepts 2 parameters: limit, location_id. Required: location_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.stations: 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.stations 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.stations 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.stations. 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.stations 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