AI agents call hourly_weather 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 retrieves historical weather data for a specified location without any side effects, modification of data, or triggering external operations beyond querying an API. It is a straightforward read operation that returns existing weather information.
From the tool's definition Tool description states 'Get the historical weather forecasts' and 'hourly history for the last 24 hours, and daily history for the last day' — purely data retrieval operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get the historical weather forecasts for the location, including hourly history for the last 24 hours, and daily history for the last day. 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 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. Nothing to install.
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 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 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.
hourly_weather is provided by the Weather MCP server (vasstavkumar/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 →