tides.noaa.predictions
Get tide predictions for a NOAA station — high/low tides, hourly, or 6-minute intervals. Returns predicted water level in feet or meters. Covers US coastlines, rivers, Great Lakes. Station IDs: 8518750 (NYC), 9414290 (SF), 8443970 (Boston) (NOAA, US Gov)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/tides.noaa.predictions.md
What tides.noaa.predictions does on Apibase
AI agents call tides.noaa.predictions 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
datum | string | — | Vertical datum: MLLW (default), MSL, NAVD, MHHW, MHW, MLW, etc. |
units | string | — | Units: "english" = feet (default), "metric" = meters |
station | string | Yes | NOAA station ID (e.g. "8518750" for The Battery NYC, "9414290" for San Francisco, "8443970" for Boston) |
end_date | string | Yes | End date in YYYYMMDD format (e.g. "20260410"). Max range: 31 days. |
interval | string | — | Prediction interval: "hilo" = high/low tides only (default), "h" = hourly, "6" = every 6 minutes |
begin_date | string | Yes | Start date in YYYYMMDD format (e.g. "20260409") |
Parameters from the server's own tool schema.
Why tides.noaa.predictions is rated Low
Tool retrieves publicly available tide prediction data with no side effects or state changes.
From the tool's definition Get tide predictions for a NOAA station — returns predicted water level.
Attacks that exploit this kind of access
The rule that runs tides.noaa.predictions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tides.noaa.predictions, this is the rule to start with:
tides.noaa.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 Apibase, apply this rule, and every tides.noaa.predictions call is checked against it from then on.
Questions about tides.noaa.predictions
Get tide predictions for a NOAA station — high/low tides, hourly, or 6-minute intervals. Returns predicted water level in feet or meters. Covers US coastlines, rivers, Great Lakes. Station IDs: 8518750 (NYC), 9414290 (SF), 8443970 (Boston) (NOAA, US Gov). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
tides.noaa.predictions accepts 6 parameters: datum, units, station, end_date, interval, begin_date. Required: station, end_date, begin_date. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for tides.noaa.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 Apibase. Nothing to install.
tides.noaa.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 tides.noaa.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 tides.noaa.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.
tides.noaa.predictions 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.
This server
Across the catalogue