tides.noaa.water_levels
Get real-time observed water levels from a NOAA station — latest reading or recent history. Returns water level in feet or meters with quality flags. Updated every 6 minutes. Covers US coastlines, rivers, Great Lakes (NOAA, US Gov)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/tides.noaa.water-levels.md
What tides.noaa.water_levels does on Apibase
AI agents call tides.noaa.water_levels 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 |
|---|---|---|---|
date | string | — | Date filter: "latest" (default, most recent reading), "today", "recent" (last 72 hours), or YYYYMMDD for specific date |
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) |
Parameters from the server's own tool schema.
Why tides.noaa.water_levels is rated Low
Tool retrieves publicly available environmental data with no state modification or side effects.
From the tool's definition Get real-time observed water levels from a NOAA station — latest reading or recent history.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs tides.noaa.water_levels 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.water_levels, this is the rule to start with:
tides.noaa.water_levels 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.water_levels call is checked against it from then on.
Questions about tides.noaa.water_levels
Get real-time observed water levels from a NOAA station — latest reading or recent history. Returns water level in feet or meters with quality flags. Updated every 6 minutes. Covers US coastlines, rivers, Great Lakes (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.water_levels accepts 4 parameters: date, datum, units, station. Required: station. 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.water_levels: 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.water_levels 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.water_levels 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.water_levels. 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.water_levels 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