proxysql_connection_pool
Get connection pool statistics per backend server. Shows connections used/free, errors, queries, bytes transferred, and latency.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/proxysql-connection-pool.md
What proxysql_connection_pool does on Mysql Mcp
AI agents call proxysql_connection_pool to retrieve information from Mysql Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why proxysql_connection_pool is rated Low
This tool queries and returns monitoring/statistics data about existing connection pools without creating, modifying, deleting, or executing any operations. It falls squarely into the Read category (retrieves data; no side effects). The blast radius is low since it only exposes operational metrics that do not directly change system state or trigger external actions.
From the tool's definition Tool retrieves 'connection pool statistics per backend server' including 'connections used/free, errors, queries, bytes transferred, and latency' — purely observational metrics with no modification or execution of commands.
Attacks that exploit this kind of access
The rule that runs proxysql_connection_pool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxysql_connection_pool, this is the rule to start with:
proxysql_connection_pool is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every proxysql_connection_pool call is checked against it from then on.
Questions about proxysql_connection_pool
Get connection pool statistics per backend server. Shows connections used/free, errors, queries, bytes transferred, and latency. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for proxysql_connection_pool: 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 Mysql Mcp. Nothing to install.
proxysql_connection_pool 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 proxysql_connection_pool 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 proxysql_connection_pool. 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.
proxysql_connection_pool is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mysql, and thousands of servers like it.
This server
Across the catalogue