// SCAN REPORT

Mysql Multi

16 tools. 10 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 3 Jul 2026

10 can modify or destroy data

6 read-only

16 tools total

Community server · catalogue entry verified 03/07/2026

How to control Mysql Multi ↓

TOOL MAP

What Mysql Multi exposes to your agents

Read (6) Write / Execute (6) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Mysql Multi tools

Destructive · Critical drop-database This tool performs an irreversible deletion operation that destroys data at scale (entire database). Destructive · High drop-index Dropping an index is an irreversible destructive operation that cannot be undone without recreating the index. Destructive · Critical drop-table DROP TABLE is a destructive operation that permanently removes a table and cannot be reversed without restoring from backups. Destructive · High remove-connection Removing a named connection from the persistent configuration is an irreversible destructive action — the connection entry is deleted from stored config.

10 of Mysql Multi's 16 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Mysql Multi

PolicyLayer is an MCP gateway — it sits between your AI agents and Mysql Multi, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "drop-database": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add-connection": {
    "limits": [
      {
        "counter": "add-connection_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "describe-table": {
    "limits": [
      {
        "counter": "describe-table_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Mysql Multi — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MYSQL MULTI →

Instant setup, no code required.

FULL CATALOGUE

All 16 Mysql Multi tools

DESTRUCTIVE 4 tools

Destructive drop-database Drop a database Destructive drop-index Drop an index from a table Destructive drop-table Drop a table Destructive remove-connection Remove a named database connection from the config

EXECUTE 2 tools

Execute alter-table Alter a table using a full ALTER TABLE SQL statement Execute execute Run any SQL statement (INSERT, UPDATE, DELETE, DDL, etc.) and return affected rows

WRITE 4 tools

Write add-connection Add a new named database connection to the config Write create-database Create a new database Write create-index Create an index using a full CREATE INDEX SQL statement Write create-table Create a table using a full CREATE TABLE SQL statement

READ 6 tools

Read describe-table Describe a table Read list-connections List all configured database connections (passwords hidden) Read list-databases List all databases on the server Read list-tables List all tables in a database Read query Run a SELECT query and return rows as JSON Read test-connection Test a named database connection

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Mysql Multi

Can an AI agent delete data through the Mysql Multi MCP server? +

Yes. The Mysql Multi server exposes 4 destructive tools including drop-database, drop-index, drop-table. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Mysql Multi? +

The Mysql Multi server has 4 write tools including add-connection, create-database, create-index. 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 Multi.

How many tools does the Mysql Multi MCP server expose? +

16 tools across 4 categories: Destructive, Execute, Read, Write. 6 are read-only. 10 can modify, create, or delete data.

How do I enforce a policy on Mysql Multi? +

Register the Mysql Multi 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.

Enforce policy on every Mysql Multi tool call.

Deterministic rules across all 16 Mysql Multi tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MYSQL MULTI →

Instant setup, no code required.

16 Mysql Multi tools catalogued and risk-classified — across an index of 43,000+ MCP servers.