transform_coordinates

THE RISK

High Risk

Why transform_coordinates needs a policy

This tool executes a coordinate transformation computation between different coordinate reference systems (CRS). It performs an active operation/calculation rather than simply retrieving stored data, making it Execute. The blast radius is low since it only transforms coordinate values and has no side effects on stored data or external systems.

From the tool's definition 'Transform coordinates between CRS' — performs a coordinate reference system transformation operation

Documented attack patterns abuse exactly the kind of access transform_coordinates gives an agent:

POLICY

How to control transform_coordinates

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 transform_coordinates:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transform_coordinates": {
      "limits": [
        {
          "counter": "transform_coordinates_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

transform_coordinates stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register GIS MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GIS MCP Server tools

Execute build_and_transform_weights Build and transform spatial weights in one step. Parameters: - data_path: Path to Execute ols_with_spatial_diagnostics_safe Safe MCP pipeline: Read shapefile, build/load W, convert numeric, check NaNs, run OLS. Execute adbscan Adaptive DBSCAN clustering (requires coordinates, no dependent_var). Execute raster_algebra raster_algebra Execute snap_geometry Snap one geometry to another using shapely.ops.snap. Args: geometry1: WKT stri Execute focal_statistics Compute focal (moving window) statistics on a raster. Args: raster_path: Path Write build_transform_and_save_weights Pipeline: Read shapefile, build spatial weights, optionally transform, and save to file. Write scale_geometry Scale a geometry.

All 98 GIS MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in GIS MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about transform_coordinates

What does the transform_coordinates tool do? +

Transform coordinates between CRS. It is categorised as a Execute tool in the GIS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on transform_coordinates? +

Register the GIS MCP Server MCP server in PolicyLayer and add a rule for transform_coordinates: 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.

What risk level is transform_coordinates? +

transform_coordinates is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit transform_coordinates? +

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

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

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

Enforce policy on every GIS MCP Server tool call.

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.

CHECK YOUR STACK →