connect_by_profile · MySQL MCP Server MCP: Risk & Policy

WHAT IT DOES

What connect_by_profile does on MySQL MCP Server

AI agents invoke connect_by_profile to trigger actions in MySQL MCP 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_by_profile needs a policy

Connecting to a database is an external operation that initiates a session and enables subsequent SQL execution. It is not purely reading data, nor is it writing or destroying anything, but it does trigger a stateful external operation. Misuse could expose a database to unauthorized access or enable further destructive queries, warranting medium severity.

From the tool's definition 「保存済み接続プロファイルを使用してデータベースに接続します」— establishes a database connection using a saved profile; 'connect' triggers an external operation (opening a live DB session).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_by_profile Rate-limited

connect_by_profile 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_by_profile": {
      "limits": [
        {
          "counter": "connect_by_profile_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 MySQL MCP Server, so you can run agents against it safely.

FAQ

Questions about connect_by_profile

What does the connect_by_profile tool do? +

保存済み接続プロファイルを使用してデータベースに接続します. It is categorised as a Execute tool in the MySQL MCP 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_by_profile? +

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

What risk level is connect_by_profile? +

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

Can I rate-limit connect_by_profile? +

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

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

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