connect_db · MCP MySQL Server MCP: Risk & Policy

WHAT IT DOES

What connect_db does on MCP MySQL Server

AI agents invoke connect_db to trigger actions in MCP MySQL Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why connect_db needs a policy

Connecting to a database is an external operation that initiates a session with a remote system. It is not purely a read (no data is retrieved) nor a write (no data is modified), but it executes an external action — establishing a live connection — whose effects (session state, credential exposure, network activity) depend on the arguments provided.

From the tool's definition 'Connect to MySQL database using URL or config' — establishes an active database connection using provided credentials/configuration

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_db Rate-limited

connect_db stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect_db": {
      "limits": [
        {
          "counter": "connect_db_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP MySQL Server, so you can run agents against it safely.

FAQ

Questions about connect_db

What does the connect_db tool do? +

Connect to MySQL database using URL or config. It is categorised as a Execute tool in the MCP MySQL Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on connect_db? +

Register the MCP MySQL Server MCP server in PolicyLayer and add a rule for connect_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 MCP MySQL Server. Nothing to install.

What risk level is connect_db? +

connect_db is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit connect_db? +

Yes. Add a rate_limit block to the connect_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.

How do I block connect_db completely? +

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

What MCP server provides connect_db? +

connect_db is provided by the MCP MySQL Server MCP server (kevinbin/mcp-mysql-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.