Get historical weather data for a specific date from 1 January 2010 onwards. Returns daily summary and full hourly breakdown. Useful for past weather lookups, analytics, and backtesting.
AI agents call get_history to retrieve information from WeatherAPI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical weather information without creating, modifying, deleting, or executing external operations. It is purely informational and poses minimal security risk—an AI agent cannot cause harm by looking up past weather data. Classification as Read is appropriate.
From the tool's definition Tool is named 'get_history' and described as retrieving 'historical weather data for a specific date' with 'daily summary and full hourly breakdown.' The verb 'Get' and action of 'returns' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get historical weather data for a specific date from 1 January 2010 onwards. Returns daily summary and full hourly breakdown. Useful for past weather lookups, analytics, and backtesting. It is categorised as a Read tool in the WeatherAPI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WeatherAPI MCP Server MCP server in PolicyLayer and add a rule for get_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 WeatherAPI MCP Server. Nothing to install.
get_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 get_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 get_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.
get_history is provided by the WeatherAPI MCP Server MCP server (weatherapicom/weatherapi-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 →