This record as markdown: /tools/mukul975-mysql-mcp-server/drop-stored-procedure.md
What drop_stored_procedure does on Mysql
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.
Why drop_stored_procedure is rated Critical
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.
Attacks that exploit this kind of access
The rule that runs drop_stored_procedure 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 drop_stored_procedure, this is the rule to start with:
drop_stored_procedure 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, apply this rule, and every drop_stored_procedure call is checked against it from then on.
Questions about drop_stored_procedure
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.
More on Mysql, and thousands of servers like it.
Across the catalogue