Historical daily weather observations (NOAA GHCN-Daily) for one station + date range (≤366 days): max/min/avg temperature °C, precipitation/snow mm, wind m/s. Records back to the 1800s — actual measured values for
AI agents call climate.station-history to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval tool with no side effects. It fetches historical weather records without creating, modifying, deleting, or executing any operations. The pay-per-call settlement model (noted in server description) does not change the tool's functional category—it is still a read operation. Severity is low because retrieving historical weather data presents minimal risk of misuse by an AI agent.
From the tool's definition Tool retrieves 'historical daily weather observations' with specific metrics (temperature, precipitation, snow, wind) for a given station and date range. No modification, deletion, or execution of code is described.
Attacks that exploit this kind of access
Historical daily weather observations (NOAA GHCN-Daily) for one station + date range (≤366 days): max/min/avg temperature °C, precipitation/snow mm, wind m/s. Records back to the 1800s — actual measured values for. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for climate.station-history: 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 Mcp. Nothing to install.
climate.station-history 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 climate.station-history 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 climate.station-history. 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.
climate.station-history is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →