AI agents call gm_lag to retrieve information from GIS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
GIS spatial lag operations are commonly used for read-only analysis—computing spatial statistics or weights based on neighboring features. No evidence suggests data creation, modification, deletion, or external execution. The lack of description reduces confidence, but the context strongly implies a spatial analysis operation rather than a destructive or financial action.
From the tool's definition Tool name 'gm_lag' with empty description; inferred from sibling tools on GIS MCP server (buffer, clip_raster_with_shapefile, calculate_geodetic_distance, etc.) which are geospatial analysis operations.
Documented attack patterns abuse exactly the kind of access gm_lag gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GIS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gm_lag:
{
"version": "1",
"default": "deny",
"tools": {
"gm_lag": {}
}
}gm_lag is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
gm_lag. It is categorised as a Read tool in the GIS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GIS MCP Server MCP server in PolicyLayer and add a rule for gm_lag: 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 GIS MCP Server. Nothing to install.
gm_lag 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 gm_lag 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 gm_lag. 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.
gm_lag is provided by the GIS MCP Server MCP server (mahdin75/gis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GIS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
98 GIS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.