mysql_spatial_transform
Transform a geometry from one spatial reference system to another.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-spatial-transform.md
What mysql_spatial_transform does on Mysql Mcp
AI agents invoke mysql_spatial_transform to trigger actions in Mysql 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.
Why mysql_spatial_transform is rated High
This tool executes a spatial transformation algorithm on geometric data. While the transformation itself is typically reversible and does not permanently modify stored data (making it less severe than Destructive), it qualifies as Execute because it triggers external computational operations whose effects depend on the input arguments (source geometry, target spatial reference system).
From the tool's definition Tool performs a transformation operation on geometry data across spatial reference systems. The description indicates active computation/transformation of data rather than passive retrieval, and the tool name includes 'transform' which implies an operation…
Attacks that exploit this kind of access
The rule that runs mysql_spatial_transform safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_spatial_transform, this is the rule to start with:
mysql_spatial_transform 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_spatial_transform call is checked against it from then on.
Questions about mysql_spatial_transform
Transform a geometry from one spatial reference system to another. It is categorised as a Execute tool in the Mysql Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_spatial_transform: 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 Mysql Mcp. Nothing to install.
mysql_spatial_transform 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 mysql_spatial_transform 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 mysql_spatial_transform. 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.
mysql_spatial_transform is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mysql, and thousands of servers like it.
Across the catalogue