# LP_Get_Elevation

Get the elevation in metres at a specific lat/lon coordinate. Available on all tiers including Free.

Agent View of the PolicyLayer registry record for `LP_Get_Elevation`. HTML page: https://policylayer.com/tools/com-geospatialsystem-location-profile/lp-get-elevation

## Facts

- Tool: `LP_Get_Elevation`
- Server: Geospatial System — Location Profile (`https://api.geospatialsystem.com/mcp`) — https://policylayer.com/tools/com-geospatialsystem-location-profile.md
- Homepage: https://github.com/https://api.geospatialsystem.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3 (3 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `lat` | number | yes | Latitude in decimal degrees (WGS-84). |
| `lon` | number | yes | Longitude in decimal degrees (WGS-84). |
| `dataset_id` | string | yes | Dataset identifier (see list_datasets). |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "LP_Get_Elevation",
    "arguments": {
      "lat": 0,
      "lon": 0,
      "dataset_id": "<dataset_id>"
    }
  }
}
```

## Why LP_Get_Elevation is rated Low

This tool queries publicly available geospatial elevation data at a specified location and returns a single value. It performs no write, delete, execute, or financial operations. The data returned is non-sensitive topographic information. Misuse by an AI agent would be limited to potentially making many requests (DoS concern) or requesting many coordinates, but the tool itself has minimal blast radius.

From the tool's own definition: "Tool name 'LP_Get_Elevation' and description 'Get the elevation in metres at a specific lat/lon coordinate' indicate a retrieval operation with no data modification or side effects."

## Use case

AI agents call LP_Get_Elevation to retrieve information from Geospatial System — Location Profile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Geospatial System — Location Profile:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "LP_Get_Elevation": {}
  }
}
```

## Other tools on Geospatial System — Location Profile (8)

- `list_datasets` — Read — https://policylayer.com/tools/com-geospatialsystem-location-profile/list-datasets.md
- `LP_Get_Elevation_Batch` — Read — https://policylayer.com/tools/com-geospatialsystem-location-profile/lp-get-elevation-batch.md
- `LP_Get_Elevation_Chart` — Read — https://policylayer.com/tools/com-geospatialsystem-location-profile/lp-get-elevation-chart.md
- `LP_Get_Elevation_Stats` — Read — https://policylayer.com/tools/com-geospatialsystem-location-profile/lp-get-elevation-stats.md
- `LP_Get_Slope_Chart` — Read — https://policylayer.com/tools/com-geospatialsystem-location-profile/lp-get-slope-chart.md
- `LP_Get_Slope_Stats` — Read — https://policylayer.com/tools/com-geospatialsystem-location-profile/lp-get-slope-stats.md
- `LP_Get_Terrain_3D` — Read — https://policylayer.com/tools/com-geospatialsystem-location-profile/lp-get-terrain-3d.md
- `LP_Get_Terrain_Map` — Read — https://policylayer.com/tools/com-geospatialsystem-location-profile/lp-get-terrain-map.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-geospatialsystem-location-profile · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-geospatialsystem-location-profile