meteo_school_check
AI agents call meteo_school_check 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.
The tool is part of a read-only weather data server (MeteoSwiss). The name pattern 'meteo_school_check' suggests it queries or checks weather-related school data (likely closures due to weather). Given sibling tools are data retrieval operations (meteo_current, meteo_forecast, meteo_stations, meteo_warnings), this tool almost certainly retrieves data with no side effects.
From the tool's definition Tool name 'meteo_school_check' suggests a query or lookup operation. Server context indicates weather/climate data access. No description provided to confirm specific action.
Attacks that exploit this kind of access
meteo_school_check. 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_school_check: 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_school_check 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_school_check 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_school_check. 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_school_check 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 →