AI agents call mysql_drop_user to permanently remove resources in Mcp Windows — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation that removes a MySQL user account permanently. Although the blast radius is limited to database user management (not data deletion itself), it meets the Destructive category definition as it removes an identity/resource that cannot be easily recovered and represents a material loss of system access configuration.
From the tool's definition Tool name 'mysql_drop_user' explicitly performs a DROP operation on a MySQL user account. The description 'Drop a MySQL user' confirms irreversible deletion of a database user identity, which cannot be undone without administrative recreation.
Documented attack patterns abuse exactly the kind of access mysql_drop_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_drop_user:
{
"version": "1",
"default": "deny",
"hide": [
"mysql_drop_user"
]
}mysql_drop_user disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Drop a MySQL user. It is categorised as a Destructive tool in the Mcp Windows MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Windows 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 Mcp Windows. Nothing to install.
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.
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.
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.
mysql_drop_user is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.