AI agents invoke transform_coordinates to trigger actions in QGIS MCP. 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.
While coordinate transformation itself is mathematically deterministic and does not modify persistent data in QGIS projects, it is fundamentally an operation that executes code/algorithms in response to user input. The tool accepts parameters (coordinates and CRS specifications) and triggers computational execution.
From the tool's definition Tool performs coordinate transformation operations in QGIS, which involves computational execution on geospatial data. The tool 'transform_coordinates' executes a spatial operation that processes input coordinates and produces output based on algorithm logic.
Attacks that exploit this kind of access
Transform coordinates between CRS. Accepts a point {x, y},. It is categorised as a Execute tool in the QGIS MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the QGIS 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 QGIS MCP. Nothing to install.
transform_coordinates is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
transform_coordinates is provided by the QGIS MCP server (nkarasiak/qgis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →