AI agents call get_weather_forecast to retrieve information from Weather MCP Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves weather forecast data from OpenWeatherMap API with no side effects, data modification, code execution, or destructive operations. It is a simple data query matching the Read category. Severity is low because misuse has no financial, operational, or security impact—it only returns weather information.
From the tool's definition Tool name 'get_weather_forecast' indicates retrieval of forecast data. Server description confirms it provides 'forecasts' and enables 'queries about current conditions, forecasts'; sibling tools (get_current_weather, get_historical_weather, get_air_quality,…
Documented attack patterns abuse exactly the kind of access get_weather_forecast gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Weather MCP Tool, and nothing reaches the server without passing your rules. This is the rule we recommend for get_weather_forecast:
{
"version": "1",
"default": "deny",
"tools": {
"get_weather_forecast": {}
}
}get_weather_forecast 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_forecast. It is categorised as a Read tool in the Weather MCP Tool MCP Server, which means it retrieves data without modifying state.
Register the Weather MCP Tool MCP server in PolicyLayer and add a rule for get_weather_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 Weather MCP Tool. Nothing to install.
get_weather_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_weather_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_weather_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_weather_forecast is provided by the Weather MCP Tool MCP server (saintdoresh/weather-mcp-claudedesktop). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Weather MCP Tool, 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.
6 Weather MCP Tool tools catalogued and risk-classified — across an index of 43,000+ MCP servers.