open_elevation_lookup
Get elevation in meters for given coordinates from Open Elevation API.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/open-elevation-lookup.md
What open_elevation_lookup does on UnClick
AI agents call open_elevation_lookup to retrieve information from UnClick 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 |
|---|---|---|---|
latitude | number | Yes | Latitude. |
longitude | number | Yes | Longitude. |
Parameters from the server's own tool schema.
Why open_elevation_lookup is rated Low
This tool purely retrieves geographic elevation data for coordinates from an external read-only API. It has no side effects, creates no data, and cannot be misused to cause significant harm.
From the tool's definition 'Get elevation in meters for given coordinates from Open Elevation API'
Attacks that exploit this kind of access
The rule that runs open_elevation_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For open_elevation_lookup, this is the rule to start with:
open_elevation_lookup 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 UnClick, apply this rule, and every open_elevation_lookup call is checked against it from then on.
Questions about open_elevation_lookup
Get elevation in meters for given coordinates from Open Elevation API. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
open_elevation_lookup accepts 2 parameters: latitude, longitude. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for open_elevation_lookup: 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 UnClick. Nothing to install.
open_elevation_lookup 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 open_elevation_lookup 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 open_elevation_lookup. 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.
open_elevation_lookup is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue