opentopodata.elevation.ocean
Get ocean floor depth (metres, negative values below sea level) at a lat/lon coordinate using the GEBCO 2020 global bathymetric dataset (450m resolution). Returns depth in metres; negative values indicate depth below sea level, positive values indicate land elevation above sea level. Use for mari...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opentopodata.elevation.ocean.md
What opentopodata.elevation.ocean does on Apibase
AI agents call opentopodata.elevation.ocean 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 |
|---|---|---|---|
lat | number | Yes | Latitude of the ocean/sea point (-90 to 90) |
lon | number | Yes | Longitude of the ocean/sea point (-180 to 180) |
interpolation | string | — | Interpolation method: bilinear (default) or nearest |
Parameters from the server's own tool schema.
Why opentopodata.elevation.ocean is rated Low
Retrieves bathymetric data with no side effects, write operations, or resource-moving capabilities.
From the tool's definition Get ocean floor depth at lat/lon coordinate from GEBCO 2020 dataset
Attacks that exploit this kind of access
The rule that runs opentopodata.elevation.ocean 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 opentopodata.elevation.ocean, this is the rule to start with:
opentopodata.elevation.ocean 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 opentopodata.elevation.ocean call is checked against it from then on.
Questions about opentopodata.elevation.ocean
Get ocean floor depth (metres, negative values below sea level) at a lat/lon coordinate using the GEBCO 2020 global bathymetric dataset (450m resolution). Returns depth in metres; negative values indicate depth below sea level, positive values indicate land elevation above sea level. Use for marine navigation planning, submarine cable routing, oceanographic research, and coastal engineering. MIT licence, no auth, no upstream cost. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
opentopodata.elevation.ocean accepts 3 parameters: lat, lon, interpolation. Required: lat, lon. 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 opentopodata.elevation.ocean: 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.
opentopodata.elevation.ocean 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 opentopodata.elevation.ocean 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 opentopodata.elevation.ocean. 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.
opentopodata.elevation.ocean 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