Get hour-by-hour weather forecast for up to 7 days (168 hours). Returns detailed hourly predictions including temperature, feels-like temperature, humidity, precipitation, weather conditions, wind speed, direction, and gusts. Perfect for planning daily activities or tracking weather changes throu...
AI agents call get_hourly_weather to retrieve information from Weather MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and returns forecasted weather information. It accepts parameters (city name or coordinates) for querying but makes no changes to data, executes no external operations with unpredictable effects, and poses no financial or destructive risk. A misused AI call would at worst generate unnecessary API requests, classified as low severity.
From the tool's definition Tool retrieves weather forecast data ('Get hour-by-hour weather forecast', 'Returns detailed hourly predictions') with no modification or side effects. Data is read-only querying of Open-Meteo API.
Attacks that exploit this kind of access
Get hour-by-hour weather forecast for up to 7 days (168 hours). Returns detailed hourly predictions including temperature, feels-like temperature, humidity, precipitation, weather conditions, wind speed, direction, and gusts. Perfect for planning daily activities or tracking weather changes throughout the day. Accepts either city name OR latitude/longitude coordinates. It is categorised as a Read tool in the Weather MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Weather MCP Server MCP server in PolicyLayer and add a rule for get_hourly_weather: 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 MCP Server. Nothing to install.
get_hourly_weather 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_hourly_weather 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_hourly_weather. 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_hourly_weather is provided by the Weather MCP Server MCP server (shayrylmae/weather-mcp-server). 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 →