gebco.elevation.profile
Get seafloor depth or land elevation for up to 15 latitude/longitude points in one call from the GEBCO global bathymetric grid — useful for building a depth/elevation profile along a route or transect (e.g. a shipping lane or hiking trail). Returns elevation in meters relative to sea level for ea...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gebco.elevation.profile.md
What gebco.elevation.profile does on Apibase
AI agents call gebco.elevation.profile 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 |
|---|---|---|---|
points | array | Yes | Between 2 and 15 {lat, lon} points to query, e.g. a route or transect across the seafloor. |
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.profile is rated Low
Queries public domain elevation data with no side effects or modification capabilities.
From the tool's definition Get seafloor depth or land elevation for up to 15 latitude/longitude points
Attacks that exploit this kind of access
The rule that runs gebco.elevation.profile 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.profile, this is the rule to start with:
gebco.elevation.profile 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.profile call is checked against it from then on.
Questions about gebco.elevation.profile
Get seafloor depth or land elevation for up to 15 latitude/longitude points in one call from the GEBCO global bathymetric grid — useful for building a depth/elevation profile along a route or transect (e.g. a shipping lane or hiking trail). Returns elevation in meters relative to sea level for each point, in the same order as the input. Optionally query "sub_ice_topo" to get bedrock topography beneath 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.profile accepts 2 parameters: points, surface. Required: points. 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.profile: 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.profile 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.profile 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.profile. 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.profile 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