Connect to MySQL database (optional if environment variables are set)
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.
Connecting to a database is an external operation that opens a persistent session/connection to a MySQL server. It is not a simple read or write of data, but rather triggers an external side effect (network connection, authentication, resource allocation on the DB server). It is reversible (connections can be closed), so it does not qualify as Destructive.
From the tool's definition 'Connect to MySQL database' — establishes an external database connection, triggering a network operation and session lifecycle management
Documented attack patterns abuse exactly the kind of access connect_db gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP MySQL Server, and nothing reaches the server without passing your rules. This is the rule we recommend for connect_db:
{
"version": "1",
"default": "deny",
"tools": {
"connect_db": {
"limits": [
{
"counter": "connect_db_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Connect to MySQL database (optional if environment variables are set). 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.
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.
connect_db is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
connect_db is provided by the MCP MySQL Server MCP server (malove86/mcp-mysql-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP MySQL Server, 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.
4 MCP MySQL Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.