Current + multi-day forecast from Open-Meteo. days_ahead 0=today only (clamped 0-7).
AI agents call weather to retrieve information from Nexus Core without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward weather data retrieval tool that queries an external weather API (Open-Meteo) and returns forecast information. It has no side effects, does not modify or delete data, does not execute code or commands, and does not involve financial transactions. The clamped range on days_ahead indicates safe input validation. Misuse poses minimal risk to system integrity.
From the tool's definition Tool retrieves 'Current + multi-day forecast from Open-Meteo' with no modification, creation, deletion, or execution capabilities. The parameter 'days_ahead' is a simple query filter (0-7 range).
Attacks that exploit this kind of access
Current + multi-day forecast from Open-Meteo. days_ahead 0=today only (clamped 0-7). It is categorised as a Read tool in the Nexus Core MCP Server, which means it retrieves data without modifying state.
Register the Nexus Core 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 Nexus Core. 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 Nexus Core MCP server (noumenon-ai/nexus-core). 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 →