flood_forecast
Get river discharge flood forecast from Open-Meteo.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/flood-forecast.md
What flood_forecast does on UnClick
AI agents call flood_forecast to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
days | number | — | Forecast days (default 7, max 92). |
latitude | number | Yes | Location latitude. |
longitude | number | Yes | Location longitude. |
Parameters from the server's own tool schema.
Why flood_forecast is rated Low
This tool retrieves meteorological forecast data from an external service (Open-Meteo). It has no side effects, does not modify data, execute code, delete anything, or involve financial transactions. The worst-case misuse scenario is retrieving irrelevant or excessive flood forecast data, which poses minimal security risk. Classified as Read with low severity.
From the tool's definition Tool name 'flood_forecast' and description 'Get river discharge flood forecast from Open-Meteo' indicates a data retrieval operation from a weather/hydrological API. Uses verb 'Get' which is a read-only operation with no modification or execution of code.
Attacks that exploit this kind of access
The rule that runs flood_forecast safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For flood_forecast, this is the rule to start with:
flood_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 UnClick, apply this rule, and every flood_forecast call is checked against it from then on.
Questions about flood_forecast
Get river discharge flood forecast from Open-Meteo. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
flood_forecast accepts 3 parameters: days, latitude, longitude. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for flood_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 UnClick. Nothing to install.
flood_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 flood_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 flood_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.
flood_forecast is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue