This record as markdown: /tools/mukul975-mysql-mcp-server/drop-partition.md
What drop_partition does on Mysql
AI agents call drop_partition 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_partition is rated Critical
Dropping a partition removes data and structural elements from a table in an irreversible manner. This is a destructive operation that cannot be easily undone and may result in data loss. Even though the server description claims to provide 'read-only queries,' this tool clearly performs a destructive write operation. The high severity reflects the potential for significant data loss if misused by an AI agent.
From the tool's definition Tool name is 'drop_partition' and description states it will 'Drop a partition from a table.' The verb 'drop' in SQL contexts refers to irreversible deletion of database objects.
Attacks that exploit this kind of access
The rule that runs drop_partition 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_partition, this is the rule to start with:
drop_partition 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_partition call is checked against it from then on.
Questions about drop_partition
Drop a partition 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 drop_partition: 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_partition 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_partition 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_partition. 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_partition 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