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

LP_Get_Terrain_Map

Generate a composite terrain map: Google Hybrid satellite (EPSG:3857) + smoothed contours with labels + flow-direction arrows + location pin. All layers are reprojected to EPSG:3857 — no overlay mismatch. Requires Pro key. Supports PNG.

SERVERGeospatial System — Location Profile SOURCEhttps://api.geospatialsystem.com/mcp
Low RISK CLASS
Category Read
Parameters 63 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-map.md

What LP_Get_Terrain_Map does on Geospatial System — Location Profile

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

ParameterTypeRequiredDescription
fmt string Output format — 'png'.
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 → 41×41 px area).
n_arrows integer Flow arrow grid density (default 11).
dataset_id string Yes Dataset identifier.

Parameters from the server's own tool schema.

Why LP_Get_Terrain_Map is rated Low

This is a retrieval and visualization tool that queries existing geospatial datasets and returns a formatted map image. While it requires a Pro API key (access control), the operation itself is read-only with no side effects, no code execution, no data modification, and no irreversible actions. The tool falls squarely into the Read category.

From the tool's definition Tool generates and returns composite terrain maps (satellite imagery, contours, flow arrows, location pins) with no capability to modify, delete, or execute operations.

Questions about LP_Get_Terrain_Map

What does the LP_Get_Terrain_Map tool do? +

Generate a composite terrain map: Google Hybrid satellite (EPSG:3857) + smoothed contours with labels + flow-direction arrows + location pin. All layers are reprojected to EPSG:3857 — no overlay mismatch. Requires Pro key. Supports PNG. 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_Map accept? +

LP_Get_Terrain_Map accepts 6 parameters: fmt, lat, lon, offset, n_arrows, dataset_id. 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_Map? +

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

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

Can I rate-limit LP_Get_Terrain_Map? +

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

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

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

// 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 Geospatial System — Location Profile'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.