transform_crs · LocuSync Server MCP: Risk & Policy

WHAT IT DOES

What transform_crs does on LocuSync Server

AI agents invoke transform_crs to trigger actions in LocuSync Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why transform_crs needs a policy

Transforming coordinate reference systems is a computational operation that processes and modifies spatial data coordinates. This falls under Execute rather than Write because it transforms data in-place during processing rather than creating new persistent records. However, the empty description limits confidence—if it modifies stored geometries, it could be Write.

From the tool's definition Tool name 'transform_crs' (transform coordinate reference system) is a geospatial operation that executes coordinate transformations. The sibling tools list includes 'crs_info' and context indicates GIS file processing and coordinate transformations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transform_crs Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LocuSync Server, so you can run agents against it safely.

FAQ

Questions about transform_crs

What does the transform_crs tool do? +

transform_crs. It is categorised as a Execute tool in the LocuSync 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_crs? +

Register the LocuSync Server MCP server in PolicyLayer and add a rule for transform_crs: 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 LocuSync Server. Nothing to install.

What risk level is transform_crs? +

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

Can I rate-limit transform_crs? +

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

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

transform_crs is provided by the LocuSync Server MCP server (matbel91765/gis-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.