mysql_doc_drop_collection
Drop a document collection.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-doc-drop-collection.md
What mysql_doc_drop_collection does on Mysql Mcp
AI agents call mysql_doc_drop_collection 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_doc_drop_collection is rated Critical
This tool performs an irreversible deletion of a document collection. Dropping a collection removes all associated data and cannot be undone without a backup restore. This is a destructive operation with high blast radius if invoked by an AI agent on the wrong collection, potentially causing data loss and service disruption.
From the tool's definition Tool name explicitly contains 'drop' and description states 'Drop a document collection.' The verb 'drop' in MySQL/database contexts is a destructive operation that irreversibly removes database objects and their data.
Attacks that exploit this kind of access
The rule that runs mysql_doc_drop_collection 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_doc_drop_collection, this is the rule to start with:
mysql_doc_drop_collection 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_doc_drop_collection call is checked against it from then on.
Questions about mysql_doc_drop_collection
Drop a document collection. 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_doc_drop_collection: 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_doc_drop_collection 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_doc_drop_collection 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_doc_drop_collection. 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_doc_drop_collection 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