获取当前 MySQL 默认连接状态。查询前可先调用此工具判断服务启动时的预配置连接是否已可用；若已连接，直接使用 mysql_query 等工具，无需先调用 mysql_connect。
AI agents call mysql_connection_status to retrieve information from Db without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves connection status information about an existing MySQL connection. It performs a read-only query with no side effects, making it a Read category risk. Severity is low because checking connection status poses minimal risk—it cannot modify data, execute arbitrary code, or cause harm even if misused by an AI agent.
From the tool's definition Tool name contains 'status'; description states it "获取当前 MySQL 默认连接状态" (gets current MySQL default connection status) and "查询前可先调用此工具判断" (can be called before querying to check if preconfigured connection is available). No mutation, execution, or side effects.
Documented attack patterns abuse exactly the kind of access mysql_connection_status 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_connection_status:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_connection_status": {}
}
}mysql_connection_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
获取当前 MySQL 默认连接状态。查询前可先调用此工具判断服务启动时的预配置连接是否已可用；若已连接，直接使用 mysql_query 等工具，无需先调用 mysql_connect。. It is categorised as a Read tool in the Db MCP Server, which means it retrieves data without modifying state.
Register the Db MCP server in PolicyLayer and add a rule for mysql_connection_status: 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_connection_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mysql_connection_status 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_connection_status. 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_connection_status 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.