连接到 MySQL 数据库（支持连接池）。仅在服务启动时未预配置 MySQL，或你需要覆盖当前默认连接时使用。
AI agents use mysql_connect to create or update resources in Db — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Db environment.
This tool establishes or overrides a MySQL database connection. It doesn't query or modify data directly, but it writes/modifies the server's connection state and can override existing preconfigured connections. It is reversible (connections can be closed/changed), so Write is appropriate rather than Destructive.
From the tool's definition 连接到 MySQL 数据库（支持连接池）。仅在服务启动时未预配置 MySQL，或你需要覆盖当前默认连接时使用。
Documented attack patterns abuse exactly the kind of access mysql_connect gives an agent:
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_connect:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_connect": {
"limits": [
{
"counter": "mysql_connect_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mysql_connect stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
连接到 MySQL 数据库（支持连接池）。仅在服务启动时未预配置 MySQL，或你需要覆盖当前默认连接时使用。. It is categorised as a Write tool in the Db MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Db MCP server in PolicyLayer and add a rule for mysql_connect: 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.
mysql_connect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mysql_connect 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.
Set action: deny in the PolicyLayer policy for mysql_connect. 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.
mysql_connect 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.
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.