AI agents call get_utm_zone 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.
This tool performs a simple lookup/calculation to determine the UTM (Universal Transverse Mercator) zone for provided coordinates. It retrieves information without modifying any data, executing arbitrary code, or causing side effects. This is a pure read operation typical of geospatial utility functions used for coordinate system reference.
From the tool's definition Tool name 'get_utm_zone' and description 'Get UTM zone for given coordinates' indicate a query operation that retrieves UTM zone information based on input coordinates. No data modification, deletion, or execution of external operations is involved.
Documented attack patterns abuse exactly the kind of access get_utm_zone 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 get_utm_zone:
{
"version": "1",
"default": "deny",
"tools": {
"get_utm_zone": {}
}
} get_utm_zone 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.
Get UTM zone for given coordinates. 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 get_utm_zone: 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.
get_utm_zone 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 get_utm_zone 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 get_utm_zone. 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.
get_utm_zone 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.