meteo_climate_normals
AI agents call meteo_climate_normals to retrieve information from Pypi:meteoswiss without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Climate normals are historical reference datasets used for comparison and analysis. The tool retrieves pre-computed data with no side effects, no code execution, no data modification, and no financial impact. This is a classic read operation. Low severity due to public weather data nature and read-only access pattern.
From the tool's definition Tool name 'meteo_climate_normals' indicates retrieval of climate normal data (historical averages/reference values). Sibling tools on the server (meteo_current, meteo_forecast, meteo_stations, meteo_warnings) are all read-only data retrieval operations.
Attacks that exploit this kind of access
meteo_climate_normals. It is categorised as a Read tool in the Pypi:meteoswiss MCP Server, which means it retrieves data without modifying state.
Register the Pypi:meteoswiss MCP server in PolicyLayer and add a rule for meteo_climate_normals: 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 Pypi:meteoswiss. Nothing to install.
meteo_climate_normals 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 meteo_climate_normals 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 meteo_climate_normals. 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.
meteo_climate_normals is provided by the Pypi:meteoswiss MCP server (malkreide/meteoswiss-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →