223 tools. 66 can modify or destroy data without limits.
14 destructive tools with no built-in limits. Policy required.
Last updated:
Community server · catalogue entry checked 28/06/2026
Running more than one server? Check your whole stack →
66 of Mysql Mcp's 223 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.
PolicyLayer is an MCP gateway — it sits between your AI agents and Mysql Mcp, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"mysql_audit_restore_backup": {
"deny_if": [
{
"conditions": [],
"on_deny": "Blocked by default. Requires approval."
}
]
}
} Destructive tools should never be available to autonomous agents without human approval.
{
"mysql_add_partition": {
"limits": [
{
"counter": "mysql_add_partition_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"mysql_audit_diff_backup": {
"limits": [
{
"counter": "mysql_audit_diff_backup_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Instant setup, no code required.
Other MCP servers with similar tools — same risk classification, starter policies for each.
Yes. The Mysql Mcp server exposes 14 destructive tools including mysql_audit_restore_backup, mysql_cascade_simulator, mysql_doc_drop_collection. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.
The Mysql Mcp server has 38 write tools including mysql_add_partition, mysql_append_insight, mysql_collation_convert. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Mysql Mcp.
223 tools across 4 categories: Destructive, Execute, Read, Write. 157 are read-only. 66 can modify, create, or delete data.
Register the Mysql MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 223 Mysql Mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Instant setup, no code required.
223 Mysql Mcp tools catalogued and risk-classified — across an index of 46,500+ MCP servers.
These policies come from Mysql's registry record.
The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →