New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

opentopodata.elevation.point

Get land surface elevation (metres above sea level) for a single latitude/longitude coordinate. Supports three global datasets: srtm90m (NASA SRTM 90m resolution, default), srtm30m (NASA SRTM 30m), and aster30m (ASTER 30m, best for high-altitude regions like Everest). Returns elevation in metres ...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 42 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opentopodata.elevation.point.md

What opentopodata.elevation.point does on Apibase

AI agents call opentopodata.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.

ParameterTypeRequiredDescription
lat number Yes Latitude of the point (-90 to 90)
lon number Yes Longitude of the point (-180 to 180)
dataset string — Elevation dataset: srtm90m (NASA SRTM 90m, default), srtm30m (NASA SRTM 30m), aster30m (ASTER 30m, good for high mountains)
interpolation string — Interpolation method: bilinear (default, smoother) or nearest (raw pixel value)

Parameters from the server's own tool schema.

Why opentopodata.elevation.point is rated Low

Retrieves public geospatial elevation data without modification or side effects.

From the tool's definition Get land surface elevation for a single latitude/longitude coordinate. Returns elevation in metres.

Questions about opentopodata.elevation.point

What does the opentopodata.elevation.point tool do? +

Get land surface elevation (metres above sea level) for a single latitude/longitude coordinate. Supports three global datasets: srtm90m (NASA SRTM 90m resolution, default), srtm30m (NASA SRTM 30m), and aster30m (ASTER 30m, best for high-altitude regions like Everest). Returns elevation in metres with the dataset name and the snapped coordinates. Use for terrain analysis, hiking route planning, flight-path clearance checks, and GIS workflows. 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.

What parameters does opentopodata.elevation.point accept? +

opentopodata.elevation.point 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.

How do I enforce a policy on opentopodata.elevation.point? +

Register the Apibase MCP server in PolicyLayer and add a rule for opentopodata.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.

What risk level is opentopodata.elevation.point? +

opentopodata.elevation.point is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit opentopodata.elevation.point? +

Yes. Add a rate_limit block to the opentopodata.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.

How do I block opentopodata.elevation.point completely? +

Set action: deny in the PolicyLayer policy for opentopodata.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.

What MCP server provides opentopodata.elevation.point? +

opentopodata.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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.