get_weather_by_datetime_range
AI agents call get_weather_by_datetime_range 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 retrieves historical or forecast weather data within a specified datetime range. No mutation, deletion, execution, or financial impact is possible. The Open-Meteo API backend is a read-only weather data service.
From the tool's definition Tool name 'get_weather_by_datetime_range' indicates data retrieval for a date range. Server description states it allows users to 'retrieve weather data for date ranges.' Sibling tools include 'get_current_weather', 'get_forecast', and 'get_alerts', all…
Attacks that exploit this kind of access
get_weather_by_datetime_range. 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_weather_by_datetime_range: 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_weather_by_datetime_range 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_weather_by_datetime_range 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_weather_by_datetime_range. 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_weather_by_datetime_range is provided by the Weather MCP Server MCP server (theshypika/mcp-servers). 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 →