AI agents call drop_stored_function 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 function permanently removes it from the database and cannot be undone without a backup restore. This is an irreversible destructive action. Although the server description claims to focus on 'read-only queries,' the presence of this tool and several others (drop_event, alter_event, create_function, create_role, create_user_with_ssl, etc.) contradicts that claim and indicates the server actually…
From the tool's definition Tool name 'drop_stored_function' combined with description 'Drop a stored function' indicates permanent deletion of a database object. The word 'drop' is a standard SQL command for irreversible removal.
Documented attack patterns abuse exactly the kind of access drop_stored_function 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_function:
{
"version": "1",
"default": "deny",
"hide": [
"drop_stored_function"
]
}drop_stored_function 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 function. 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_function: 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_function 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_function 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_function. 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_function 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.