opentopodata.elevation.high_res
Get high-resolution elevation for a single coordinate using regional datasets: ned10m (USGS National Elevation Dataset 10m, continental US only) or eudem25m (EU-DEM 25m, Europe only). Returns elevation in metres with dataset name. Use ned10m for US urban/terrain analysis and eudem25m for European...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opentopodata.elevation.high-res.md
What opentopodata.elevation.high_res does on Apibase
AI agents call opentopodata.elevation.high_res 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 (-90 to 90) |
lon | number | Yes | Longitude of the point (-180 to 180) |
dataset | string | — | High-resolution dataset: ned10m (USGS NED 10m, continental US only) or eudem25m (EU-DEM 25m, Europe only). Defaults to ned10m. |
interpolation | string | — | Interpolation method: bilinear (default) or nearest |
Parameters from the server's own tool schema.
Why opentopodata.elevation.high_res is rated Low
Queries elevation data from public geographic datasets; returns information without side effects.
From the tool's definition Get high-resolution elevation for a single coordinate using regional datasets
Attacks that exploit this kind of access
The rule that runs opentopodata.elevation.high_res 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.high_res, this is the rule to start with:
opentopodata.elevation.high_res 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.high_res call is checked against it from then on.
Questions about opentopodata.elevation.high_res
Get high-resolution elevation for a single coordinate using regional datasets: ned10m (USGS National Elevation Dataset 10m, continental US only) or eudem25m (EU-DEM 25m, Europe only). Returns elevation in metres with dataset name. Use ned10m for US urban/terrain analysis and eudem25m for European geospatial workflows requiring higher accuracy than SRTM. 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.high_res accepts 4 parameters: lat, lon, dataset, 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.high_res: 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.high_res 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.high_res 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.high_res. 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.high_res 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