获取当前 MySQL 连接池状态（如果使用连接池）。若服务启动时已预配置并启用了连接池，也会返回默认连接的状态。
AI agents call mysql_pool_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 retrieves diagnostic information about connection pool state—a read-only operation with no side effects. It queries metadata about active connections but does not execute arbitrary queries, modify data, or trigger destructive operations. The blast radius of misuse is minimal; an attacker could only gather information about pool configuration and connection counts.
From the tool's definition Tool name 'mysql_pool_status' and description '获取当前 MySQL 连接池状态' (get current MySQL connection pool status) indicate retrieval of connection pool metadata and status information.
Documented attack patterns abuse exactly the kind of access mysql_pool_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_pool_status:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_pool_status": {}
}
}mysql_pool_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 连接池状态（如果使用连接池）。若服务启动时已预配置并启用了连接池，也会返回默认连接的状态。. 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_pool_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_pool_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_pool_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_pool_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_pool_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.