sun_times
Sunrise, sunset, solar noon, day length, civil / nautical / astronomical twilight, golden hour and blue hour for any place and date (NOAA solar calculator equations, about a minute of accuracy), with polar day / night handling, observer elevation correction and local times in any IANA zone. Optio...
This record as markdown: /tools/com-it-scorptech-x402/sun-times.md
What sun_times does on ScorpTech x402 API
AI agents call sun_times 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 for sun position (azimuth / elevation), or "now" |
tz | string | — | IANA time zone for the output |
lat | number | Yes | |
lon | number | Yes | |
date | string | — | Local date YYYY-MM-DD (default today in tz) |
elevation | number | — | Observer height above the horizon in metres (earlier sunrise / later sunset) |
Parameters from the server's own tool schema.
Why sun_times is rated Low
Even though sun_times 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 sun_times 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 sun_times, this is the rule to start with:
sun_times 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 sun_times call is checked against it from then on.
Questions about sun_times
Sunrise, sunset, solar noon, day length, civil / nautical / astronomical twilight, golden hour and blue hour for any place and date (NOAA solar calculator equations, about a minute of accuracy), with polar day / night handling, observer elevation correction and local times in any IANA zone. Optionally the sun's azimuth and elevation (refraction-corrected) at a given moment. Offline. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/sun-times. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
sun_times accepts 6 parameters: at, tz, lat, lon, date, elevation. Required: 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 sun_times: 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.
sun_times 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 sun_times 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 sun_times. 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.
sun_times 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