Get historical weather for a location on a given date (YYYY-MM-DD).
AI agents call weather_history to retrieve information from Weather without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns historical weather data for a specified location and date. It is purely informational with no side effects, data modification, or irreversible actions. It fits the Read category definition: retrieves or queries data with no side effects.
From the tool's definition Tool description states 'Get historical weather for a location on a given date' — a retrieval operation with no modification, deletion, or execution of external actions.
Documented attack patterns abuse exactly the kind of access weather_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Weather, and nothing reaches the server without passing your rules. This is the rule we recommend for weather_history:
{
"version": "1",
"default": "deny",
"tools": {
"weather_history": {}
}
}weather_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get historical weather for a location on a given date (YYYY-MM-DD). It is categorised as a Read tool in the Weather MCP Server, which means it retrieves data without modifying state.
Register the Weather 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 Weather. 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 Weather MCP server (sjanax01/weather-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Weather, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Weather tools catalogued and risk-classified — across an index of 43,000+ MCP servers.