delete_data

THE RISK

Critical Risk

Why delete_data needs a policy

The delete_data tool irreversibly removes data from the database. Deletion cannot be undone without backups or transaction rollback. This is a core destructive operation.

From the tool's definition Tool name: 'delete_data'. Description: 'Deletes data from a table in the MySQL database.' Server description confirms the tool supports 'deleting records'.

Documented attack patterns abuse exactly the kind of access delete_data gives an agent:

POLICY

How to control delete_data

PolicyLayer is an MCP gateway — it sits between your AI agents and MySQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_data:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_data"
  ]
}

delete_data disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register MySQL MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MySQL MCP Server tools

Destructive execute_sql Executes any non-SELECT SQL statement (e.g., ALTER TABLE, DROP, etc.) Write create_table Creates a new table in the MySQL database. Write insert_data Inserts data into a table in the MySQL database. Write update_data Updates data in a table in the MySQL database. Read run_sql_query Executes a read-only SQL query (SELECT statements only) against the MySQL database.

All 6 MySQL MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MySQL MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_data

What does the delete_data tool do? +

Deletes data from a table in the MySQL database. It is categorised as a Destructive tool in the MySQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_data? +

Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for delete_data: 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 MCP Server. Nothing to install.

What risk level is delete_data? +

delete_data is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_data? +

Yes. Add a rate_limit block to the delete_data 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.

How do I block delete_data completely? +

Set action: deny in the PolicyLayer policy for delete_data. 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.

What MCP server provides delete_data? +

delete_data is provided by the MySQL MCP Server MCP server (michael7736/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MySQL MCP Server tool call.

Start from MySQL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →