LP_Get_Slope_Chart
Generate a range-box chart showing terrain slope Min/Avg/Max across three neighbourhood window sizes. Returns a URL to the chart image. Requires Pro key. Supports PNG / SVG / PDF.
This record as markdown: /tools/com-geospatialsystem-location-profile/lp-get-slope-chart.md
What LP_Get_Slope_Chart does on Geospatial System — Location Profile
AI agents call LP_Get_Slope_Chart 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', 'svg', or 'pdf'. |
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_Slope_Chart is rated Low
LP_Get_Slope_Chart performs a read-only operation: it computes statistics from geospatial datasets and returns a visualization URL. No data is created, modified, deleted, or written back to the system. No code execution, financial transactions, or destructive operations are involved. The tool requires authentication (Pro key) but this is access control, not a risk escalator.
From the tool's definition Tool generates and returns a chart visualization URL showing terrain slope statistics (Min/Avg/Max). The description explicitly states it 'Returns a URL to the chart image' with no mention of data modification, deletion, or external state changes.
Attacks that exploit this kind of access
The rule that runs LP_Get_Slope_Chart 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_Slope_Chart, this is the rule to start with:
LP_Get_Slope_Chart 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_Slope_Chart call is checked against it from then on.
Questions about LP_Get_Slope_Chart
Generate a range-box chart showing terrain slope Min/Avg/Max across three neighbourhood window sizes. Returns a URL to the chart image. Requires Pro key. Supports PNG / SVG / PDF. 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_Slope_Chart accepts 4 parameters: fmt, 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_Slope_Chart: 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_Slope_Chart 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_Slope_Chart 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_Slope_Chart. 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_Slope_Chart 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