New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

metno.astronomy.sunrise

Get precise sunrise, sunset, solar noon, and solar midnight times for any global coordinate and date from the Norwegian Meteorological Institute Sunrise 3.0 API. For the Sun: returns sunrise time + azimuth, sunset time + azimuth, solar noon elevation and visibility. For the Moon: returns moonrise...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 53 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/metno.astronomy.sunrise.md

What metno.astronomy.sunrise does on Apibase

AI agents call metno.astronomy.sunrise 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.

ParameterTypeRequiredDescription
lat number Yes Latitude in decimal degrees (e.g. 59.91 for Oslo, 51.5 for London)
lon number Yes Longitude in decimal degrees (e.g. 10.75 for Oslo, -0.12 for London)
body string — Celestial body: "sun" returns sunrise/sunset/solarnoon (default), "moon" returns moonrise/moonset/phase.
date string Yes Date to compute times for in ISO 8601 format YYYY-MM-DD (e.g. "2026-06-24")
offset string — UTC offset for local time output in ±HH:MM format (e.g. "+02:00" for CEST). Defaults to UTC.

Parameters from the server's own tool schema.

Why metno.astronomy.sunrise is rated Low

Tool retrieves astronomical data with no side effects, state changes, or financial implications.

From the tool's definition Get precise sunrise, sunset, solar noon times for any global coordinate and date

Risk signalsAccepts raw HTML/template content (body)

Questions about metno.astronomy.sunrise

What does the metno.astronomy.sunrise tool do? +

Get precise sunrise, sunset, solar noon, and solar midnight times for any global coordinate and date from the Norwegian Meteorological Institute Sunrise 3.0 API. For the Sun: returns sunrise time + azimuth, sunset time + azimuth, solar noon elevation and visibility. For the Moon: returns moonrise, moonset, high moon, low moon, and lunar phase (0–360°). Supports UTC offset for local time output. Global coverage; handles polar day/night (midnight sun / polar night). CC BY 4.0 + NLOD 2.0, no auth, no upstream cost. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does metno.astronomy.sunrise accept? +

metno.astronomy.sunrise accepts 5 parameters: lat, lon, body, date, offset. Required: lat, lon, date. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on metno.astronomy.sunrise? +

Register the Apibase MCP server in PolicyLayer and add a rule for metno.astronomy.sunrise: 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 metno.astronomy.sunrise? +

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

Can I rate-limit metno.astronomy.sunrise? +

Yes. Add a rate_limit block to the metno.astronomy.sunrise 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 metno.astronomy.sunrise completely? +

Set action: deny in the PolicyLayer policy for metno.astronomy.sunrise. 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 metno.astronomy.sunrise? +

metno.astronomy.sunrise 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.