Get weather information for a specified city between start and end dates.
AI agents call get_weather_byDateTimeRange 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
city | string | — | The name of the city to fetch weather information for, PLEASE NOTE English name only, if the parameter city isn't English please translate to English before inv |
end_date | string | — | End date in format YYYY-MM-DD , please follow ISO 8601 format |
start_date | string | — | Start date in format YYYY-MM-DD, please follow ISO 8601 format |
Parameters from the server's own tool schema.
This tool retrieves historical or forecasted weather data within a date range. It performs a read-only query against the Open-Meteo API with no capability to modify, delete, execute code, or trigger external operations. The blast radius of misuse is minimal—an agent could only request excessive queries or retrieve weather data for arbitrary locations, neither of which causes damage or irreversible consequences.
From the tool's definition Tool name and description indicate data retrieval only: 'Get weather information for a specified city between start and end dates.' The verb 'Get' and the context of the Weather MCP Server (which retrieves real-time weather data) confirm this is a query…
Documented attack patterns abuse exactly the kind of access get_weather_byDateTimeRange gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Weather MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_weather_byDateTimeRange:
{
"version": "1",
"default": "deny",
"tools": {
"get_weather_byDateTimeRange": {}
}
}get_weather_byDateTimeRange is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get weather information for a specified city between start and end dates. It is categorised as a Read tool in the Weather MCP Server MCP Server, which means it retrieves data without modifying state.
get_weather_byDateTimeRange accepts 3 parameters: city, end_date, start_date. The full parameter table on this page comes from the server's own tool schema.
Register the Weather MCP Server MCP server in PolicyLayer and add a rule for get_weather_byDateTimeRange: 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_byDateTimeRange 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_byDateTimeRange 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_byDateTimeRange. 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_byDateTimeRange is provided by the Weather MCP Server MCP server (isdaniel/mcp_weather_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Weather MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Weather MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.