Get historical weather data from ERA5 reanalysis (1940-present) for specific coordinates and date range.
AI agents call weather_archive to retrieve information from Open Meteo 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 an external API. It is a pure read/query operation with no side effects, no data modification, and no irreversible actions. Misuse potential is minimal — it only returns weather information.
From the tool's definition 'Get historical weather data from ERA5 reanalysis (1940-present) for specific coordinates and date range'
Attacks that exploit this kind of access
Get historical weather data from ERA5 reanalysis (1940-present) for specific coordinates and date range. It is categorised as a Read tool in the Open Meteo MCP Server, which means it retrieves data without modifying state.
Register the Open Meteo MCP server in PolicyLayer and add a rule for weather_archive: 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 Open Meteo. Nothing to install.
weather_archive 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_archive 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_archive. 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_archive is provided by the Open Meteo MCP server (windsornguyen/open-meteo-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 →