Normalize the orientation/order of a geometry using shapely.normalize. Args: geometry: WKT string of the geometry. Returns: Dictionary with status, message, and normalized geometry as WKT.
AI agents call normalize_geometry 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.
normalize_geometry performs a deterministic geometric computation that reorders/normalizes the orientation of geometry coordinates. This is a read-like operation: it consumes input, performs calculations, and returns output without creating, modifying, deleting, or executing external operations. No data is persisted or irreversibly changed.
From the tool's definition The tool normalizes geometry orientation/order using shapely.normalize and returns the result without modifying persistent data.
Documented attack patterns abuse exactly the kind of access normalize_geometry 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 normalize_geometry:
{
"version": "1",
"default": "deny",
"tools": {
"normalize_geometry": {}
}
}normalize_geometry 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.
Normalize the orientation/order of a geometry using shapely.normalize. Args: geometry: WKT string of the geometry. Returns: Dictionary with status, message, and normalized geometry as WKT. 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 normalize_geometry: 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.
normalize_geometry 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 normalize_geometry 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 normalize_geometry. 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.
normalize_geometry 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.