sunrisesunset.astronomy.range

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 64 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/sunrisesunset.astronomy.range.md

WHAT IT DOES

What sunrisesunset.astronomy.range does on Apibase

AI agents call sunrisesunset.astronomy.range 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
`lat`	number	Yes	Latitude of the target location (-90 to 90). Positive = North, Negative = South.
`lng`	number	Yes	Longitude of the target location (-180 to 180). Positive = East, Negative = West.
`date_end`	string	Yes	End date of range in ISO format YYYY-MM-DD (e.g. 2026-06-30). Maximum 365 days from start date.
`timezone`	string	—	IANA timezone name for output times (e.g. America/New_York, Europe/London, Asia/Tokyo). Auto-detected from lat/lng if omitted.
`date_start`	string	Yes	Start date of range in ISO format YYYY-MM-DD (e.g. 2026-06-01).
`time_format`	string	—	Time output format: "0"=12-hour AM/PM (e.g. 5:26:02 AM), "1"=24-hour (e.g. 05:26:02), "2"=Unix timestamp seconds. Defaults to "0".

Parameters from the server's own tool schema.

RISK

Why sunrisesunset.astronomy.range is rated Low

Retrieves astronomical data with no side effects, modifications, or external state changes.

From the tool's definition Get sunrise/sunset/moon phase data for a date range. Returns an array of daily records.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sunrisesunset.astronomy.range 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 sunrisesunset.astronomy.range, this is the rule to start with:

sunrisesunset.astronomy.range Allowed

sunrisesunset.astronomy.range is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sunrisesunset.astronomy.range": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every sunrisesunset.astronomy.range call is checked against it from then on.

FAQ

Questions about sunrisesunset.astronomy.range

What does the sunrisesunset.astronomy.range tool do? +

Get sunrise/sunset/moon phase data for a date range of up to 365 days for any global coordinate. Returns an array of daily records each with: sunrise, sunset, solar noon, golden hour, day length, moon phase name, and moon illumination percentage. Useful for seasonal planning, photography planning, agriculture, and event scheduling. Specify date_start and date_end in YYYY-MM-DD format; max 365 days per call. No auth required; free commercial use. Source: SunriseSunset.io. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does sunrisesunset.astronomy.range accept? +

sunrisesunset.astronomy.range accepts 6 parameters: lat, lng, date_end, timezone, date_start, time_format. Required: lat, lng, date_end, date_start. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sunrisesunset.astronomy.range? +

Register the Apibase MCP server in PolicyLayer and add a rule for sunrisesunset.astronomy.range: 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.

What risk level is sunrisesunset.astronomy.range? +

sunrisesunset.astronomy.range is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sunrisesunset.astronomy.range? +

Yes. Add a rate_limit block to the sunrisesunset.astronomy.range 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.

How do I block sunrisesunset.astronomy.range completely? +

Set action: deny in the PolicyLayer policy for sunrisesunset.astronomy.range. 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.

What MCP server provides sunrisesunset.astronomy.range? +

sunrisesunset.astronomy.range 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →