AI agents call drop_stored_procedure 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.
Dropping a stored procedure irreversibly deletes a database object. This is a destructive action that cannot be undone without restoring from backups. While the blast radius is typically contained to that specific procedure (not a full database wipe), the unrecoverable nature of the deletion and the potential for disrupting dependent applications makes this a high-severity destructive action.
From the tool's definition Tool name explicitly states 'drop' (a destructive operation). Description confirms it 'Drop[s] a stored procedure' — removal of database objects that cannot be easily recovered without backups.
Documented attack patterns abuse exactly the kind of access drop_stored_procedure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mysql, and nothing reaches the server without passing your rules. This is the rule we recommend for drop_stored_procedure:
{
"version": "1",
"default": "deny",
"hide": [
"drop_stored_procedure"
]
}drop_stored_procedure 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 stored procedure. 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.
Register the Mysql MCP server in PolicyLayer and add a rule for drop_stored_procedure: 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.
drop_stored_procedure 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_stored_procedure 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_stored_procedure. 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_stored_procedure 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.
Start from Mysql, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
233 Mysql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.