AI agents call mysql_drop_foreign_key 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 foreign key constraint is a destructive operation that cannot be trivially undone—it modifies database schema in a way that alters referential integrity and requires explicit recreation to reverse. While not deleting rows, it permanently removes structural metadata. This is more severe than Write (reversible modification) and clearly falls under Destructive.
From the tool's definition Tool name explicitly contains 'drop' and description states 'Drop a foreign key constraint from a table.' The action irreversibly removes a database constraint.
Documented attack patterns abuse exactly the kind of access mysql_drop_foreign_key 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 mysql_drop_foreign_key:
{
"version": "1",
"default": "deny",
"hide": [
"mysql_drop_foreign_key"
]
}mysql_drop_foreign_key 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 foreign key constraint from a table. 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 mysql_drop_foreign_key: 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.
mysql_drop_foreign_key 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_foreign_key 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_foreign_key. 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_foreign_key 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.