gebco.elevation.point
Get the seafloor depth or land elevation at a single latitude/longitude point from the GEBCO global bathymetric grid (General Bathymetric Chart of the Oceans, IHO/IOC Seabed 2030 project). Returns elevation in meters relative to sea level — negative for ocean depth, positive for land height, e.g....
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gebco.elevation.point.md
What gebco.elevation.point does on Apibase
AI agents call gebco.elevation.point 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 in decimal degrees (e.g. 51.4769 for Greenwich). |
lon | number | Yes | Longitude in decimal degrees (e.g. -0.0005 for Greenwich). |
surface | string | — | Which GEBCO grid to query: "standard" (default) returns surface elevation, including the top of ice sheets where present; "sub_ice_topo" returns bedrock topogra |
Parameters from the server's own tool schema.
Why gebco.elevation.point is rated Low
Retrieves public domain geographic data; no side effects or data modification.
From the tool's definition Get seafloor depth or land elevation at a single latitude/longitude point
Attacks that exploit this kind of access
The rule that runs gebco.elevation.point 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 gebco.elevation.point, this is the rule to start with:
gebco.elevation.point 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 gebco.elevation.point call is checked against it from then on.
Questions about gebco.elevation.point
Get the seafloor depth or land elevation at a single latitude/longitude point from the GEBCO global bathymetric grid (General Bathymetric Chart of the Oceans, IHO/IOC Seabed 2030 project). Returns elevation in meters relative to sea level — negative for ocean depth, positive for land height, e.g. -5943 near the Mariana Trench or 2947 in the Himalayan foothills. Optionally query "sub_ice_topo" to get bedrock topography beneath Antarctic/Greenland ice sheets instead of the ice surface. Data: GEBCO WMS, public domain, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gebco.elevation.point accepts 3 parameters: lat, lon, surface. 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 gebco.elevation.point: 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.
gebco.elevation.point 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 gebco.elevation.point 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 gebco.elevation.point. 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.
gebco.elevation.point 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