meteo_current
AI agents call meteo_current 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.
This tool retrieves current weather observations from MeteoSwiss. It has no apparent ability to modify, delete, execute operations, or create financial obligations. The description is empty but the sibling tools (meteo_forecast, meteo_warnings, meteo_stations, meteo_climate_normals) and server purpose strongly indicate this is a data retrieval tool. Blast radius is minimal since it only fetches public weather data.
From the tool's definition Tool name is 'meteo_current' and is part of a server described as providing 'access to Swiss weather and climate data from MeteoSwiss, including current observations, forecasts, and warnings.' The 'current' component refers to current observations, which are…
Attacks that exploit this kind of access
meteo_current. 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_current: 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_current 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_current 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_current. 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_current 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 →