opentopo.elevation.point
Query terrain elevation (in metres) at a specific latitude/longitude coordinate using global Digital Elevation Model (DEM) datasets. Supports SRTMGL1 (NASA SRTM 30m, default), COP30 (Copernicus 30m), AW3D30 (ALOS 30m), NASADEM (30m reprocessed), SRTM15Plus (500m global bathymetry), and more. Retu...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opentopo.elevation.point.md
What opentopo.elevation.point does on Apibase
AI agents call opentopo.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 of the point to query (-90 to 90 decimal degrees) |
lon | number | Yes | Longitude of the point to query (-180 to 180 decimal degrees) |
dataset | string | — | Global DEM dataset to query. SRTMGL1 = NASA SRTM 30m (default, global). COP30 = Copernicus 30m (high accuracy). AW3D30 = ALOS World 3D 30m. NASADEM = NASA 30m r |
Parameters from the server's own tool schema.
Why opentopo.elevation.point is rated Low
Tool retrieves publicly available geospatial elevation data without modifying state or executing arbitrary code.
From the tool's definition Query terrain elevation at specific latitude/longitude coordinate, returns elevation data.
Attacks that exploit this kind of access
The rule that runs opentopo.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 opentopo.elevation.point, this is the rule to start with:
opentopo.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 opentopo.elevation.point call is checked against it from then on.
Questions about opentopo.elevation.point
Query terrain elevation (in metres) at a specific latitude/longitude coordinate using global Digital Elevation Model (DEM) datasets. Supports SRTMGL1 (NASA SRTM 30m, default), COP30 (Copernicus 30m), AW3D30 (ALOS 30m), NASADEM (30m reprocessed), SRTM15Plus (500m global bathymetry), and more. Returns elevation_m plus dataset resolution info. Source: OpenTopography / USGS 3DEP, CC BY 4.0, free registration (5K req/day). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
opentopo.elevation.point accepts 3 parameters: lat, lon, dataset. 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 opentopo.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.
opentopo.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 opentopo.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 opentopo.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.
opentopo.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