New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

marine.ocean.swell

Hourly swell forecast at an ocean coordinate — swell wave height (m), swell direction (°), and swell period (s) for up to 16 days. Swell consists of wind-generated waves that have propagated far from their origin, typically with longer periods (>10s) and more regular patterns than wind-sea. High-...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 42 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/marine.ocean.swell.md

What marine.ocean.swell does on Apibase

AI agents call marine.ocean.swell 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.

ParameterTypeRequiredDescription
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.swell is rated Low

Tool retrieves ocean swell forecasts without modifying data or executing external operations.

From the tool's definition Hourly swell forecast at an ocean coordinate — retrieves weather data.

Questions about marine.ocean.swell

What does the marine.ocean.swell tool do? +

Hourly swell forecast at an ocean coordinate — swell wave height (m), swell direction (°), and swell period (s) for up to 16 days. Swell consists of wind-generated waves that have propagated far from their origin, typically with longer periods (>10s) and more regular patterns than wind-sea. High-period swell (>12s) is ideal for surfing; low-period swell (<6s) indicates local chop. Swell direction indicates where the swell is coming from (degrees clockwise from north). Useful for surf forecasting, sailing passage planning, and aquaculture site assessment. 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.

What parameters does marine.ocean.swell accept? +

marine.ocean.swell 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.

How do I enforce a policy on marine.ocean.swell? +

Register the Apibase MCP server in PolicyLayer and add a rule for marine.ocean.swell: 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.

What risk level is marine.ocean.swell? +

marine.ocean.swell is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit marine.ocean.swell? +

Yes. Add a rate_limit block to the marine.ocean.swell 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.

How do I block marine.ocean.swell completely? +

Set action: deny in the PolicyLayer policy for marine.ocean.swell. 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.

What MCP server provides marine.ocean.swell? +

marine.ocean.swell 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.