mysql_spatial_create_column
Add a geometry/spatial column to an existing table.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-spatial-create-column.md
What mysql_spatial_create_column does on Mysql Mcp
AI agents use mysql_spatial_create_column to create or update resources in Mysql Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mysql Mcp environment.
Why mysql_spatial_create_column is rated Medium
Adding a column to a table modifies the database schema but is reversible (the column can be dropped). This fits the Write category—it creates/modifies data structures. Severity is high because schema changes can affect application functionality, dependent views, triggers, and performance, and errors may cascade. However, it does not fall under Destructive (the change is not irreversible) or Financial.
From the tool's definition Tool name and description indicate it 'Add[s] a geometry/spatial column to an existing table.' This is a schema modification operation that creates a new column, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs mysql_spatial_create_column 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_create_column, this is the rule to start with:
mysql_spatial_create_column stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_create_column call is checked against it from then on.
Questions about mysql_spatial_create_column
Add a geometry/spatial column to an existing table. It is categorised as a Write tool in the Mysql Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_spatial_create_column: 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_create_column is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mysql_spatial_create_column 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_create_column. 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_create_column 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.
This server
Across the catalogue