mysql_drop_user

Drop a MySQL user.

SERVERMysql SOURCEmukul975/mysql-mcp-server

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/mukul975-mysql-mcp-server/mysql-drop-user.md

WHAT IT DOES

What mysql_drop_user does on Mysql

AI agents call mysql_drop_user to permanently remove resources in Mysql, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why mysql_drop_user is rated Critical

Dropping a user is a destructive action that irreversibly deletes database account credentials and access rights. This cannot be undone without manual restoration and represents a critical security and operational risk if triggered by an AI agent without proper authorization. The presence of this destructive tool on a server advertised as 'read-only' is a significant discrepancy.

From the tool's definition Tool name explicitly states 'drop' a MySQL user; 'drop' in database contexts is an irreversible deletion operation. The server description claims 'read-only queries' but this tool directly contradicts that by enabling user deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_drop_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_drop_user, this is the rule to start with:

mysql_drop_user Hidden

mysql_drop_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "mysql_drop_user"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mysql, apply this rule, and every mysql_drop_user call is checked against it from then on.

FAQ

Questions about mysql_drop_user

What does the mysql_drop_user tool do? +

Drop a MySQL user. It is categorised as a Destructive tool in the Mysql 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_drop_user? +

Register the Mysql MCP server in PolicyLayer and add a rule for mysql_drop_user: 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. Nothing to install.

What risk level is mysql_drop_user? +

mysql_drop_user 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_drop_user? +

Yes. Add a rate_limit block to the mysql_drop_user 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_drop_user completely? +

Set action: deny in the PolicyLayer policy for mysql_drop_user. 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_drop_user? +

mysql_drop_user is provided by the Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mysql, and thousands of servers like it.

This server

All 233 Mysql tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_user on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →