coops.tides.water_level
Get verified observed water level readings (at 6-minute intervals) from a NOAA CO-OPS tide gauge station. Returns time-series data with UTC timestamps, water height in feet or meters relative to the chosen datum, and data quality flags. Specify station_id and optional date range (default: last 24...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/coops.tides.water-level.md
What coops.tides.water_level does on Apibase
AI agents call coops.tides.water_level 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 for water height measurements. MLLW is the standard chart datum. Defaults to MLLW. |
limit | integer | — | Maximum number of 6-minute interval readings to return (1–500). Defaults to 120. One day has 240 readings. |
units | string | — | Unit system: english = feet, metric = meters. Defaults to english. |
end_date | string | — | End date for water level observations in YYYY-MM-DD or YYYYMMDD format (e.g. 2025-07-02). Defaults to today. Maximum range: 31 days. |
begin_date | string | — | Start date for water level observations in YYYY-MM-DD or YYYYMMDD format (e.g. 2025-07-01). Defaults to yesterday. Maximum range: 31 days. |
station_id | string | Yes | NOAA CO-OPS station ID (4–7 digits, e.g. 8443970 for Boston MA). Find station IDs with the coops.tides.stations tool. |
Parameters from the server's own tool schema.
Why coops.tides.water_level is rated Low
Retrieves historical tide gauge data with no side effects or modification capability.
From the tool's definition Get verified observed water level readings, returns time-series data, no modification capability
Attacks that exploit this kind of access
The rule that runs coops.tides.water_level 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 coops.tides.water_level, this is the rule to start with:
coops.tides.water_level 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 coops.tides.water_level call is checked against it from then on.
Questions about coops.tides.water_level
Get verified observed water level readings (at 6-minute intervals) from a NOAA CO-OPS tide gauge station. Returns time-series data with UTC timestamps, water height in feet or meters relative to the chosen datum, and data quality flags. Specify station_id and optional date range (default: last 24 hours, max range 31 days). Datum defaults to MLLW. Observed data may lag real-time by up to 6 minutes; use coops.tides.predictions for future forecasts. Useful for flood monitoring, storm surge analysis, historical tide research, and comparing observed vs. predicted tides. Source: NOAA CO-OPS — tidesandcurrents.noaa.gov. No auth, US Gov public domain. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
coops.tides.water_level accepts 6 parameters: datum, limit, units, end_date, begin_date, station_id. Required: station_id. 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 coops.tides.water_level: 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.
coops.tides.water_level 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 coops.tides.water_level 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 coops.tides.water_level. 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.
coops.tides.water_level 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