AI agents call delete_db to permanently remove resources in Skysql — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a database instance is a permanent, non-recoverable action that destroys all data contained within it. This cannot be undone without restoration from backups (if available). The blast radius is critical as loss of a production database causes immediate service outages and permanent data loss. This is the most severe category (Destructive > Execute > Write > Read).
From the tool's definition Tool name 'delete_db' with description 'Delete a DB instance from SkySQL' - the verb 'delete' combined with 'instance' indicates irreversible removal of an entire database.
Documented attack patterns abuse exactly the kind of access delete_db gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Skysql, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_db:
{
"version": "1",
"default": "deny",
"hide": [
"delete_db"
]
}delete_db 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.
Delete a DB instance from SkySQL. It is categorised as a Destructive tool in the Skysql MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Skysql MCP server in PolicyLayer and add a rule for delete_db: 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 Skysql. Nothing to install.
delete_db 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 delete_db 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 delete_db. 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.
delete_db is provided by the Skysql MCP server (skysqlinc/skysql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Skysql, 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.
8 Skysql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.