usno.astronomy.sun_moon
Get sunrise, sunset, moonrise, moonset, and transit times for any location and date. Includes civil/nautical/astronomical twilight. Used for photography golden hour, agriculture planning, outdoor events. Source: USNO.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/usno.astronomy.sun-moon.md
What usno.astronomy.sun_moon does on Apibase
AI agents call usno.astronomy.sun_moon to retrieve information from Apibase 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 |
|---|---|---|---|
date | string | Yes | Date in YYYY-MM-DD format (e.g. 2026-04-07) |
latitude | number | Yes | Latitude in decimal degrees (e.g. 40.7128 for New York) |
longitude | number | Yes | Longitude in decimal degrees (e.g. -74.0060 for New York) |
Parameters from the server's own tool schema.
Why usno.astronomy.sun_moon is rated Low
Retrieves astronomical data with no side effects or ability to modify state.
From the tool's definition Get sunrise, sunset, moonrise, moonset, transit times for any location and date.
Attacks that exploit this kind of access
The rule that runs usno.astronomy.sun_moon safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For usno.astronomy.sun_moon, this is the rule to start with:
usno.astronomy.sun_moon 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 Apibase, apply this rule, and every usno.astronomy.sun_moon call is checked against it from then on.
Questions about usno.astronomy.sun_moon
Get sunrise, sunset, moonrise, moonset, and transit times for any location and date. Includes civil/nautical/astronomical twilight. Used for photography golden hour, agriculture planning, outdoor events. Source: USNO. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
usno.astronomy.sun_moon accepts 3 parameters: date, latitude, longitude. Required: date, latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for usno.astronomy.sun_moon: 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 Apibase. Nothing to install.
usno.astronomy.sun_moon 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 usno.astronomy.sun_moon 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 usno.astronomy.sun_moon. 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.
usno.astronomy.sun_moon is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue