Get weather forecast for 1 to 14 days. Returns daily summaries (max/min/avg temp, rain chance, UV, wind) and hourly breakdowns. Also returns current conditions, astronomy data (sunrise/sunset/moon phase), and optionally weather alerts and air quality.
AI agents call get_forecast 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 performs purely informational queries against a weather API. It has no side effects, does not modify any state, and does not execute code or external operations. The worst outcome of misuse would be excessive API calls or gathering weather information for impersonation/planning purposes, but the tool itself cannot delete, modify, execute, or move money. Classified as Read with low severity.
From the tool's definition Tool retrieves weather forecast data, current conditions, astronomy data, and optionally alerts and air quality — all read operations with no modification or deletion of data. The description uses verbs like 'Get' and 'Returns', indicating data retrieval only.
Attacks that exploit this kind of access
Get weather forecast for 1 to 14 days. Returns daily summaries (max/min/avg temp, rain chance, UV, wind) and hourly breakdowns. Also returns current conditions, astronomy data (sunrise/sunset/moon phase), and optionally weather alerts and air quality. 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_forecast: 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_forecast 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_forecast 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_forecast. 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_forecast 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 →