coops.tides.stations
List active NOAA CO-OPS tide gauge stations with their IDs, names, coordinates, and metadata. Over 300 stations covering US coastal states, Puerto Rico, Pacific Islands, and the Great Lakes. Filter by state abbreviation (e.g. CA, FL, NY) to find local stations. Returns station_id, name, latitude,...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/coops.tides.stations.md
What coops.tides.stations does on Apibase
AI agents call coops.tides.stations 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 |
|---|---|---|---|
limit | integer | — | Maximum number of stations to return (1–200). Defaults to 50. |
state | string | — | Filter stations by US state abbreviation (e.g. CA, NY, FL, TX). Must be exactly 2 uppercase letters. Omit for all states. |
tidal_only | boolean | — | When true (default), return only tidal stations. Set to false to include Great Lakes and non-tidal stations. |
Parameters from the server's own tool schema.
Why coops.tides.stations is rated Low
Tool retrieves public tide station metadata without modifying data or enabling harmful operations.
From the tool's definition List active NOAA CO-OPS tide gauge stations with IDs, names, coordinates, metadata
Attacks that exploit this kind of access
The rule that runs coops.tides.stations 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.stations, this is the rule to start with:
coops.tides.stations 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.stations call is checked against it from then on.
Questions about coops.tides.stations
List active NOAA CO-OPS tide gauge stations with their IDs, names, coordinates, and metadata. Over 300 stations covering US coastal states, Puerto Rico, Pacific Islands, and the Great Lakes. Filter by state abbreviation (e.g. CA, FL, NY) to find local stations. Returns station_id, name, latitude, longitude, state, timezone, tidal flag, and forecast availability. Use the returned station_id values with coops.tides.predictions, coops.tides.water_level, and coops.tides.conditions. 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.stations accepts 3 parameters: limit, state, tidal_only. 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.stations: 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.stations 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.stations 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.stations. 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.stations 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