LP_Get_Elevation_Stats
Get elevation statistics (Min, Average, Max) for 3×3, 5×5 and 7×7 pixel windows centred on the coordinates. Requires Pro or Enterprise key.
This record as markdown: /tools/com-geospatialsystem-location-profile/lp-get-elevation-stats.md
What LP_Get_Elevation_Stats does on Geospatial System — Location Profile
AI agents call LP_Get_Elevation_Stats 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.
| 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. |
Parameters from the server's own tool schema.
Why LP_Get_Elevation_Stats is rated Low
This tool queries and returns statistical summaries (min, average, max) of elevation data for specified pixel windows. It performs read-only operations on geospatial datasets. No data is created, modified, deleted, or executed. The requirement for 'Pro or Enterprise key' is an access control measure, not a risk multiplier.
From the tool's definition Tool name 'LP_Get_Elevation_Stats' and description state it 'Get[s] elevation statistics (Min, Average, Max)' — purely retrieves computed statistics from geospatial data with no modification, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs LP_Get_Elevation_Stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Geospatial System — Location Profile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For LP_Get_Elevation_Stats, this is the rule to start with:
LP_Get_Elevation_Stats 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 Geospatial System — Location Profile, apply this rule, and every LP_Get_Elevation_Stats call is checked against it from then on.
Questions about LP_Get_Elevation_Stats
Get elevation statistics (Min, Average, Max) for 3×3, 5×5 and 7×7 pixel windows centred on the coordinates. Requires Pro or Enterprise key. It is categorised as a Read tool in the Geospatial System — Location Profile MCP Server, which means it retrieves data without modifying state.
LP_Get_Elevation_Stats accepts 3 parameters: lat, lon, dataset_id. Required: lat, lon, dataset_id. The full parameter table on this page comes from the server's own tool schema.
Register the Geospatial System — Location Profile MCP server in PolicyLayer and add a rule for LP_Get_Elevation_Stats: 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 Geospatial System — Location Profile. Nothing to install.
LP_Get_Elevation_Stats 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 LP_Get_Elevation_Stats 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 LP_Get_Elevation_Stats. 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.
LP_Get_Elevation_Stats is provided by the Geospatial System — Location Profile MCP server (https://api.geospatialsystem.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Geospatial System — Location Profile, and thousands of servers like it.
Across the catalogue