tide_predictions
Return high and low tide predictions (times and heights) from the keyless NOAA Tides & Currents (CO-OPS) public API - U.S. Government public-domain data. Give either a NOAA station id (e.g. '9414290' for San Francisco) or a lat/lon (the nearest tide-prediction station is chosen automatically). Re...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/tide-predictions.md
What tide_predictions does on Livedatalink
AI agents call tide_predictions to retrieve information from Livedatalink 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 | — | Latitude in decimal degrees. Used with lon to pick the nearest station when no station id is given. |
lon | number | — | Longitude in decimal degrees (negative west). |
datum | string | — | Tidal datum: MLLW, MSL, MHW, etc. Default MLLW. |
units | string | — | 'english' (feet) or 'metric' (meters). Default english. |
station | string | — | NOAA CO-OPS station id, e.g. '9414290'. Optional if lat and lon are given. |
end_date | string | — | End date (inclusive), 'YYYY-MM-DD'. Defaults to begin_date + 1 day. |
begin_date | string | — | Start date (inclusive), 'YYYY-MM-DD'. Defaults to today. |
Parameters from the server's own tool schema.
Why tide_predictions is rated Low
Even though tide_predictions 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 tide_predictions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tide_predictions, this is the rule to start with:
tide_predictions 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 Livedatalink, apply this rule, and every tide_predictions call is checked against it from then on.
Questions about tide_predictions
Return high and low tide predictions (times and heights) from the keyless NOAA Tides & Currents (CO-OPS) public API - U.S. Government public-domain data. Give either a NOAA station id (e.g. '9414290' for San Francisco) or a lat/lon (the nearest tide-prediction station is chosen automatically). Returns each high and low tide over the requested inclusive date range, in local station time, relative to the chosen tidal datum (default MLLW). Use it for tide tables, beach and boating planning, or coastal scheduling. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
tide_predictions accepts 7 parameters: lat, lon, datum, units, station, end_date, begin_date. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for tide_predictions: 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 Livedatalink. Nothing to install.
tide_predictions 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 tide_predictions 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 tide_predictions. 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.
tide_predictions is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue