sunrise_sunset_times
Get sunrise and sunset times for GPS coordinates.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/sunrise-sunset-times.md
What sunrise_sunset_times does on UnClick
AI agents call sunrise_sunset_times to retrieve information from UnClick 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 |
lng | number | Yes | Longitude |
date | string | — | Date (YYYY-MM-DD) or 'today' (default) |
Parameters from the server's own tool schema.
Why sunrise_sunset_times is rated Low
This is a straightforward data retrieval tool that queries and returns sunrise/sunset information. There are no side effects, no data modification, no code execution, and no financial impact. The blast radius of misuse is minimal—an agent could only retrieve potentially redundant or unwanted astronomical data. This is a classic Read category tool.
From the tool's definition The tool 'Get sunrise and sunset times for GPS coordinates' retrieves astronomical data based on input coordinates. It uses verb 'Get' indicating a read-only query operation with no modification, creation, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs sunrise_sunset_times safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sunrise_sunset_times, this is the rule to start with:
sunrise_sunset_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 UnClick, apply this rule, and every sunrise_sunset_times call is checked against it from then on.
Questions about sunrise_sunset_times
Get sunrise and sunset times for GPS coordinates. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
sunrise_sunset_times accepts 3 parameters: lat, lng, date. Required: lat, lng. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for sunrise_sunset_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 UnClick. Nothing to install.
sunrise_sunset_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 sunrise_sunset_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 sunrise_sunset_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.
sunrise_sunset_times is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue