moon_phase
Moon phase for any moment: phase name and emoji, illuminated fraction, phase angle, age in days since new moon, waxing / waning, Earth-Moon distance and apparent size, the next new moon / first quarter / full moon / last quarter (to a few minutes), and moonrise / moonset for a location and local ...
This record as markdown: /tools/com-it-scorptech-x402/moon-phase.md
What moon_phase does on ScorpTech x402 API
AI agents call moon_phase to retrieve information from ScorpTech x402 API 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 |
|---|---|---|---|
at | string | — | ISO 8601 moment (default now); a bare date means local noon in tz |
tz | string | — | IANA zone for output times |
lat | number | — | Latitude for moonrise / moonset |
lon | number | — | Longitude for moonrise / moonset |
Parameters from the server's own tool schema.
Why moon_phase is rated Low
Even though moon_phase 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 moon_phase safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For moon_phase, this is the rule to start with:
moon_phase 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 ScorpTech x402 API, apply this rule, and every moon_phase call is checked against it from then on.
Questions about moon_phase
Moon phase for any moment: phase name and emoji, illuminated fraction, phase angle, age in days since new moon, waxing / waning, Earth-Moon distance and apparent size, the next new moon / first quarter / full moon / last quarter (to a few minutes), and moonrise / moonset for a location and local date (topocentric, parallax and refraction aware). Meeus lunar theory, offline. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/moon-phase. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
moon_phase accepts 4 parameters: at, tz, lat, lon. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for moon_phase: 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 ScorpTech x402 API. Nothing to install.
moon_phase 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 moon_phase 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 moon_phase. 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.
moon_phase is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue