get_hourly_forecast
Get the hour-by-hour weather forecast (temperature, precipitation, wind) for a latitude/longitude via the Open-Meteo API — read-only, no API key needed.
This record as markdown: /tools/io-github-heznpc-iconnect/get-hourly-forecast.md
What get_hourly_forecast does on Iconnect
AI agents call get_hourly_forecast to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_hourly_forecast is rated Low
This tool queries external weather data (Open-Meteo API) and returns forecast information without modifying, deleting, or executing any operations. The read-only designation and retrieval pattern (get_) clearly indicate a Read category classification. Severity is low because misuse would only retrieve weather data, causing no harmful side effects.
From the tool's definition Tool description explicitly states 'Get the hour-by-hour weather forecast' and 'read-only, no API key needed'. The operation is a retrieval of weather data with no side effects.
Attacks that exploit this kind of access
The rule that runs get_hourly_forecast safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_hourly_forecast, this is the rule to start with:
get_hourly_forecast is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every get_hourly_forecast call is checked against it from then on.
Questions about get_hourly_forecast
Get the hour-by-hour weather forecast (temperature, precipitation, wind) for a latitude/longitude via the Open-Meteo API — read-only, no API key needed. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for get_hourly_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 Iconnect. Nothing to install.
get_hourly_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_hourly_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_hourly_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_hourly_forecast is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue