17 tools. 0 can modify or destroy data without limits.
Read-only server. Low risk, but rate limits prevent runaway API costs.
Last updated:
Community server · catalogue entry verified 03/07/2026
Running more than one server? Check your whole stack →
Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.
PolicyLayer is an MCP gateway — it sits between your AI agents and Open Meteo, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"air_quality": {
"limits": [
{
"counter": "air_quality_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Instant setup, no code required.
The Open Meteo server is primarily read-only with 17 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.
17 tools across 2 categories: Read, Write. 17 are read-only. 0 can modify, create, or delete data.
Register the Open Meteo MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 17 Open Meteo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Instant setup, no code required.
17 Open Meteo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.