Historical daily weather (ERA5, 1940→~5 days ago) for a coordinate + date range (start, end YYYY-MM-DD, ≤366 days): per-day max/min/mean temp, precipitation total + hours, max wind. Source: Open-Meteo archive (keyless).
AI agents call weather.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 tool retrieves historical weather data from the Open-Meteo archive. It is a pure read/query operation with no side effects. However, it is on a pay-per-call server settled in USDC, meaning each call has a small financial cost.
From the tool's definition Historical daily weather (ERA5, 1940→~5 days ago) for a coordinate + date range... per-day max/min/mean temp, precipitation total + hours, max wind. Source: Open-Meteo archive (keyless).
Attacks that exploit this kind of access
Historical daily weather (ERA5, 1940→~5 days ago) for a coordinate + date range (start, end YYYY-MM-DD, ≤366 days): per-day max/min/mean temp, precipitation total + hours, max wind. Source: Open-Meteo archive (keyless). 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 weather.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.
weather.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 weather.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 weather.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.
weather.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 →