Low Risk

mysql_disconnect

断开当前 MySQL 数据库连接,包括启动时已建立的默认连接。

How to control mysql_disconnect ↓

What mysql_disconnect does on Db

AI agents call mysql_disconnect as a supporting operation in Db workflows.

Low Risk

Why mysql_disconnect needs a policy

This tool disconnects a database connection. It does not read, write, execute, destroy data, or perform financial operations. Disconnecting is a session/resource management action. While it could disrupt ongoing operations, it doesn't irreversibly delete data or modify it. It falls best under 'Other' as it is purely a connection lifecycle action.

From the tool's definition 断开当前 MySQL 数据库连接,包括启动时已建立的默认连接 (Disconnect the current MySQL database connection, including the default connection established at startup)

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

How to control mysql_disconnect

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_disconnect": {
      "limits": [
        {
          "counter": "mysql_disconnect_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

mysql_disconnect gets a rate cap, and everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Db — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
SET A RULE FOR THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about mysql_disconnect

What does the mysql_disconnect tool do? +

断开当前 MySQL 数据库连接,包括启动时已建立的默认连接。. It is categorised as a Other tool in the Db MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on mysql_disconnect? +

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

What risk level is mysql_disconnect? +

mysql_disconnect is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mysql_disconnect? +

Yes. Add a rate_limit block to the mysql_disconnect 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 mysql_disconnect completely? +

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

mysql_disconnect is provided by the Db MCP server (wannanbigpig/db-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Db tool call.

Start from Db, 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.

34 Db tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.