LP_Get_Terrain_3D

Generate a 3-D perspective terrain surface map (Plotly go.Surface) coloured by elevation with a red spike pin marking the query location. Requires Pro key. Supports PNG / HTML.

SERVERGeospatial System — Location Profile SOURCEhttps://api.geospatialsystem.com/mcp

Low RISK CLASS

Category Read

Parameters 73 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-geospatialsystem-location-profile/lp-get-terrain-3d.md

WHAT IT DOES

What LP_Get_Terrain_3D does on Geospatial System — Location Profile

AI agents call LP_Get_Terrain_3D 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
`fmt`	string	—	Output format — 'png', or 'html'.
`lat`	number	Yes	Latitude in decimal degrees (WGS-84).
`lon`	number	Yes	Longitude in decimal degrees (WGS-84).
`offset`	integer	—	Half-window pixels (default 20).
`azim_angle`	number	—	Camera azimuth angle in degrees (default 135).
`dataset_id`	string	Yes	Dataset identifier.
`elev_angle`	number	—	Camera elevation angle in degrees (default 45).

Parameters from the server's own tool schema.

RISK

Why LP_Get_Terrain_3D is rated Low

This tool queries elevation and terrain data to produce a visual representation (3-D map). It has no side effects—it does not create, modify, delete, or execute operations on underlying data. The output is a read-only visualization artifact. Requires Pro key for access control but does not perform any destructive, executable, or financial operations.

From the tool's definition Tool retrieves and generates visualization data: 'Generate a 3-D perspective terrain surface map' with 'elevation' coloring and location marking. No modification, deletion, code execution, or financial transaction.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs LP_Get_Terrain_3D 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_Terrain_3D, this is the rule to start with:

LP_Get_Terrain_3D Allowed

LP_Get_Terrain_3D is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "LP_Get_Terrain_3D": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Geospatial System — Location Profile, apply this rule, and every LP_Get_Terrain_3D call is checked against it from then on.

FAQ

Questions about LP_Get_Terrain_3D

What does the LP_Get_Terrain_3D tool do? +

Generate a 3-D perspective terrain surface map (Plotly go.Surface) coloured by elevation with a red spike pin marking the query location. Requires Pro key. Supports PNG / HTML. It is categorised as a Read tool in the Geospatial System — Location Profile MCP Server, which means it retrieves data without modifying state.

What parameters does LP_Get_Terrain_3D accept? +

LP_Get_Terrain_3D accepts 7 parameters: fmt, lat, lon, offset, azim_angle, dataset_id, elev_angle. Required: lat, lon, dataset_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on LP_Get_Terrain_3D? +

Register the Geospatial System — Location Profile MCP server in PolicyLayer and add a rule for LP_Get_Terrain_3D: 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.

What risk level is LP_Get_Terrain_3D? +

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

Can I rate-limit LP_Get_Terrain_3D? +

Yes. Add a rate_limit block to the LP_Get_Terrain_3D 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 LP_Get_Terrain_3D completely? +

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

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

KEEP EXPLORING

More on Geospatial System — Location Profile, and thousands of servers like it.

This server

All 9 Geospatial System — Location Profile tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →