mysql_vector_create_index
Create an HNSW vector index for faster KNN searches (requires MySQL 9.1+).
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-vector-create-index.md
What mysql_vector_create_index does on Mysql Mcp
AI agents use mysql_vector_create_index 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_vector_create_index is rated Medium
Creating an index is a reversible write operation that modifies the database schema and persists changes, but does not irreversibly delete data or execute arbitrary code. It could impact query performance and storage if indexes are created incorrectly, justifying medium severity. High confidence due to clear 'create' intent in both name and description.
From the tool's definition Tool name includes 'create_index' and description states 'Create an HNSW vector index', which are schema modification operations that add or alter database structures.
Attacks that exploit this kind of access
The rule that runs mysql_vector_create_index 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_vector_create_index, this is the rule to start with:
mysql_vector_create_index 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_vector_create_index call is checked against it from then on.
Questions about mysql_vector_create_index
Create an HNSW vector index for faster KNN searches (requires MySQL 9.1+). 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_vector_create_index: 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_vector_create_index 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_vector_create_index 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_vector_create_index. 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_vector_create_index 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