New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

mysql_vector_delete

Delete a vector embedding by its row identifier.

SERVERMysql Mcp SOURCEoci:docker.io/writenotenow/mysql-mcp:v1.0.0
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about mysql_vector_delete

What does the mysql_vector_delete tool do? +

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.

How do I enforce a policy on mysql_vector_delete? +

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.

What risk level is mysql_vector_delete? +

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.

Can I rate-limit mysql_vector_delete? +

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.

How do I block mysql_vector_delete completely? +

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.

What MCP server provides mysql_vector_delete? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mysql's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.