sun_moon_times
skypeek: Get sunrise, sunset, twilight, moonrise and moon phase for a place and date. For satellite passes use satellite_passes. Returns sunrise, sunset, solar noon, day length and civil / nautical / astronomical twilight, plus moonrise, moonset, moon phase, illumination and distance, for a point...
This record as markdown: /tools/dev-tanod-tanod/sun-moon-times.md
What sun_moon_times does on Tanod
AI agents call sun_moon_times to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tz | object | — | IANA time zone for the date and the output (such as Asia/Manila); default UTC. |
lat | number | Yes | Latitude in degrees (-90 to 90). |
lon | number | Yes | Longitude in degrees (-180 to 180). |
date | object | — | Local date YYYY-MM-DD (1900-2100); default today. |
Parameters from the server's own tool schema.
Why sun_moon_times is rated Low
Even though sun_moon_times only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs sun_moon_times 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 sun_moon_times, this is the rule to start with:
sun_moon_times is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every sun_moon_times call is checked against it from then on.
Questions about sun_moon_times
skypeek: Get sunrise, sunset, twilight, moonrise and moon phase for a place and date. For satellite passes use satellite_passes. Returns sunrise, sunset, solar noon, day length and civil / nautical / astronomical twilight, plus moonrise, moonset, moon phase, illumination and distance, for a point and a local date, in a time zone you choose. Computed locally (Meeus series; no upstream call): sun and twilight times within about 1 minute, moonrise and moonset within about 3 minutes; sea-level horizon, terrain and weather not modelled. A bad date or time zone is a 422 (not charged). Typically under 0.2 s. Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/sunrise-sunset-moon-phase-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
sun_moon_times accepts 4 parameters: tz, lat, lon, date. 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 sun_moon_times: 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.
sun_moon_times 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 sun_moon_times 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 sun_moon_times. 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.
sun_moon_times 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.
This server
Across the catalogue