Get sun rise/set and other sun event times for a specific date and location
AI agents call get_sun_times to retrieve information from LocalTides MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves astronomical data (sunrise/sunset times) from the NOAA API. It performs a read-only query with no capability to modify, delete, or execute operations. The data returned has no financial impact and poses no security risk if misused by an agent—at worst, an agent receives inaccurate astronomical data for planning purposes.
From the tool's definition Tool name 'get_sun_times' and description 'Get sun rise/set and other sun event times for a specific date and location' indicate a pure data retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Get sun rise/set and other sun event times for a specific date and location. It is categorised as a Read tool in the LocalTides MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LocalTides MCP Server MCP server in PolicyLayer and add a rule for get_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 LocalTides MCP Server. Nothing to install.
get_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 get_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 get_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.
get_sun_times is provided by the LocalTides MCP Server MCP server (ryancardin15/noaa-tidesandcurrents-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →