Connect to MySQL database using URL or config
AI agents call connect_db as a supporting operation in MCP-MongoDB-MySQL-Server workflows.
This tool establishes a database connection but does not read, write, execute queries, or modify data. It is a connectivity/setup operation. While misconfigured connections could expose credentials or connect to unintended databases, the tool itself does not perform any data operation, placing it in 'Other'. Severity is low as it is a prerequisite step rather than a direct data action.
From the tool's definition Connect to MySQL database using URL or config
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-MongoDB-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": 60,
"scope": "grant"
}
]
}
}
} connect_db gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Connect to MySQL database using URL or config. It is categorised as a Other tool in the MCP-MongoDB-MySQL-Server MCP Server, which means it performs auxiliary operations.
Register the MCP-MongoDB-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-MongoDB-MySQL-Server. Nothing to install.
connect_db is a Other tool with low risk. Read-only tools are generally safe to allow by default.
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-MongoDB-MySQL-Server MCP server (yaoxiaolinglong/mcp-mongodb-mysql-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-MongoDB-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.
14 MCP-MongoDB-MySQL-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.