aurora_forecast
skypeek: Aurora forecast: the chance of visible aurora at a location in the next 30-90 minutes. For Kp and solar wind use get_space_weather. Returns the chance (0 to 100 percent) of visible aurora overhead at a point from NOAA SWPC's OVATION model for the next 30-90 minutes, with the current Kp, ...
This record as markdown: /tools/dev-tanod-tanod/aurora-forecast.md
What aurora_forecast does on Tanod
AI agents call aurora_forecast to permanently remove resources in Tanod, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
lat | number | Yes | Latitude in degrees (-90 to 90). |
lon | number | Yes | Longitude in degrees (-180 to 180). |
Parameters from the server's own tool schema.
Why aurora_forecast is rated Critical
An AI agent that decides to call aurora_forecast doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Tanod is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs aurora_forecast safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For aurora_forecast, this is the rule to start with:
aurora_forecast is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every aurora_forecast call is checked against it from then on.
Questions about aurora_forecast
skypeek: Aurora forecast: the chance of visible aurora at a location in the next 30-90 minutes. For Kp and solar wind use get_space_weather. Returns the chance (0 to 100 percent) of visible aurora overhead at a point from NOAA SWPC's OVATION model for the next 30-90 minutes, with the current Kp, the Sun's altitude and whether it is dark enough. Data: NOAA Space Weather Prediction Center (public domain), a derived copy, not an official NOAA product; no endorsement by NOAA or the National Weather Service is implied. The model assumes a dark, clear sky: cloud, moonlight and light pollution are not modelled. Cached up to 10 minutes. An upstream outage is a 503 upstream_unavailable (not charged). Typically under 1 s cached, a few seconds on a refresh. Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/space-weather-kp-index-aurora-api.html. It is categorised as a Destructive tool in the Tanod MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
aurora_forecast accepts 2 parameters: lat, lon. Required: lat, lon. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for aurora_forecast: 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 Tanod. Nothing to install.
aurora_forecast is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the aurora_forecast 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 aurora_forecast. 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.
aurora_forecast is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
Across the catalogue