Drop a database (DANGEROUS - requires confirmation).
AI agents call drop_database to permanently remove resources in MCP MySQL Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently and irreversibly deletes a database, which cannot be undone without restoration from backups. This represents maximal data loss within a single database scope. It is more severe than Execute or Write because the action cannot be reversed through normal operations. The explicit '(DANGEROUS)' label in the description confirms the risk assessment.
From the tool's definition Tool name is 'drop_database' and description explicitly states 'Drop a database (DANGEROUS - requires confirmation)'. The verb 'drop' in SQL context irreversibly deletes an entire database and all its contents.
Attacks that exploit this kind of access
Drop a database (DANGEROUS - requires confirmation). It is categorised as a Destructive tool in the MCP MySQL Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP MySQL Server MCP server in PolicyLayer and add a rule for drop_database: 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 MCP MySQL Server. Nothing to install.
drop_database 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 drop_database 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 drop_database. 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.
drop_database is provided by the MCP MySQL Server MCP server (kami2k1/mcp-mysql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →