usno.astronomy.moon_phases
Get all moon phase dates for a year — New Moon, First Quarter, Full Moon, Last Quarter with exact UTC timestamps. ~50 phases per year. Source: US Naval Observatory (canonical astronomical authority, US Gov public domain).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/usno.astronomy.moon-phases.md
What usno.astronomy.moon_phases does on Apibase
AI agents call usno.astronomy.moon_phases 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 |
|---|---|---|---|
year | integer | — | Year for moon phases (default: current year, e.g. 2026) |
Parameters from the server's own tool schema.
Why usno.astronomy.moon_phases is rated Low
Retrieves astronomical data with no side effects, modifications, or external operations triggered.
From the tool's definition Get all moon phase dates for a year with exact UTC timestamps.
Attacks that exploit this kind of access
The rule that runs usno.astronomy.moon_phases 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.moon_phases, this is the rule to start with:
usno.astronomy.moon_phases 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.moon_phases call is checked against it from then on.
Questions about usno.astronomy.moon_phases
Get all moon phase dates for a year — New Moon, First Quarter, Full Moon, Last Quarter with exact UTC timestamps. ~50 phases per year. Source: US Naval Observatory (canonical astronomical authority, US Gov public domain). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
usno.astronomy.moon_phases accepts 1 parameter: year. 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.moon_phases: 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.moon_phases 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.moon_phases 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.moon_phases. 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.moon_phases 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