weather
Get current weather observations for a German city. Sourced from the Deutscher Wetterdienst (DWD): temperature, wind, precipitation and related fields. Read-only, current conditions only (not a forecast). For warnings use get_city_resource(slug, resource='weather-warnings'). For a broader questio...
This record as markdown: /tools/dev-infranode-infranode/weather.md
What weather does on InfraNode
AI agents call weather to retrieve information from InfraNode 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 |
|---|---|---|---|
slug | string | Yes | City identifier, e.g. 'berlin' or 'hamburg'. Resolved leniently: the German name with or without umlauts, any casing, a common English exonym or short form also |
Parameters from the server's own tool schema.
Why weather is rated Low
This tool queries and returns weather data for a German city without modifying, deleting, or executing any operations. The explicit 'read-only' designation and lack of any parameters that could trigger side effects confirm this is a simple data retrieval operation with minimal security risk.
From the tool's definition Tool description explicitly states 'Read-only, current conditions only'. Retrieves weather observations (temperature, wind, precipitation) from DWD with no side effects.
Attacks that exploit this kind of access
The rule that runs weather safely
PolicyLayer is an MCP gateway: it sits between your AI agents and InfraNode, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For weather, this is the rule to start with:
weather 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 InfraNode, apply this rule, and every weather call is checked against it from then on.
Questions about weather
Get current weather observations for a German city. Sourced from the Deutscher Wetterdienst (DWD): temperature, wind, precipitation and related fields. Read-only, current conditions only (not a forecast). For warnings use get_city_resource(slug, resource='weather-warnings'). For a broader question about the city (not just weather) use get_city_overview instead, which already includes a live weather highlight. It is categorised as a Read tool in the InfraNode MCP Server, which means it retrieves data without modifying state.
weather accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the InfraNode MCP server in PolicyLayer and add a rule for weather: 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 InfraNode. Nothing to install.
weather 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 weather 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 weather. 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.
weather is provided by the InfraNode MCP server (https://mcp.infranode.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on InfraNode, and thousands of servers like it.
This server
Across the catalogue