mysql_vector_delete
Delete a vector embedding by its row identifier.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-vector-delete.md
What mysql_vector_delete does on Mysql Mcp
AI agents call mysql_vector_delete to permanently remove resources in Mysql Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why mysql_vector_delete is rated Critical
This tool permanently removes data (a vector embedding) from the database indexed by row identifier. Deletion is an irreversible operation that cannot be undone without a restore, making it Destructive rather than Write. High severity due to potential loss of important embeddings and downstream model/search functionality that depends on them.
From the tool's definition Tool name and description: 'Delete a vector embedding by its row identifier' — uses the verb 'Delete' which indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs mysql_vector_delete 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_delete, this is the rule to start with:
mysql_vector_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_vector_delete call is checked against it from then on.
Questions about mysql_vector_delete
Delete a vector embedding by its row identifier. It is categorised as a Destructive tool in the Mysql Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_vector_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the mysql_vector_delete 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_delete. 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_delete 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