delete-data

THE RISK

Critical Risk

Why delete-data needs a policy

Deletion of database records is an irreversible operation that cannot be undone without a backup or transaction rollback. This meets the definition of Destructive. While other tools on the server (drop-table, execute-sql) could also be destructive, delete-data specifically targets data deletion. The empty description reduces confidence slightly, but the name and server context make the intent clear.

From the tool's definition Tool is named 'delete-data' and belongs to a server that explicitly permits 'deletion of database tables and records.' The tool name directly indicates irreversible removal of data.

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 drop-table drop-table Execute execute-sql execute-sql Write create-table create-table Write insert-data insert-data Write update-data update-data Read query-data query-data

All 7 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? +

delete-data. 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 (log6262635/mcp-mysql). 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 →