marine.ocean.waves
Hourly wave conditions forecast at an ocean coordinate — wave height (m), wave direction (°), and wave period (s) for up to 16 days. Wave height is significant wave height (average of the highest third of waves). Wave direction is the mean direction from which waves are coming (degrees clockwise ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/marine.ocean.waves.md
What marine.ocean.waves does on Apibase
AI agents call marine.ocean.waves 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 |
|---|---|---|---|
latitude | number | Yes | Latitude of the ocean location in decimal degrees (e.g. 51.5 for English Channel, 48.5 for Bay of Biscay). Must be over open water — land coordinates return nul |
timezone | string | — | Timezone for the returned time values (e.g. "UTC", "Europe/London", "America/New_York"). Defaults to UTC. |
longitude | number | Yes | Longitude of the ocean location in decimal degrees (e.g. -14.0 for Atlantic, 2.3 for North Sea). |
forecast_days | integer | — | Number of days to forecast (1–16). Defaults to 7. Hourly data is returned for each day. |
Parameters from the server's own tool schema.
Why marine.ocean.waves is rated Low
Retrieves meteorological forecast data for specified coordinates; no state modification, purely informational query.
From the tool's definition hourly wave conditions forecast at ocean coordinate; no side effects
Attacks that exploit this kind of access
The rule that runs marine.ocean.waves 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 marine.ocean.waves, this is the rule to start with:
marine.ocean.waves 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 marine.ocean.waves call is checked against it from then on.
Questions about marine.ocean.waves
Hourly wave conditions forecast at an ocean coordinate — wave height (m), wave direction (°), and wave period (s) for up to 16 days. Wave height is significant wave height (average of the highest third of waves). Wave direction is the mean direction from which waves are coming (degrees clockwise from north). Wave period is the mean time between successive wave crests in seconds. Useful for surfing spot reports, ferry/vessel routing, coastal engineering assessments, and storm monitoring. Source: Open-Meteo Marine API, CC BY 4.0, no authentication required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
marine.ocean.waves accepts 4 parameters: latitude, timezone, longitude, forecast_days. Required: latitude, longitude. 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 marine.ocean.waves: 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.
marine.ocean.waves 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 marine.ocean.waves 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 marine.ocean.waves. 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.
marine.ocean.waves 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