proxysql_servers

List configured backend MySQL servers from mysql_servers table. Shows hostgroup, hostname, port, status, and weights.

SERVERMysql Mcp SOURCEoci:docker.io/writenotenow/mysql-mcp:v1.0.0

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/proxysql-servers.md

WHAT IT DOES

What proxysql_servers does on Mysql Mcp

AI agents call proxysql_servers 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.

RISK

Why proxysql_servers is rated Low

This tool retrieves and displays configuration information from the mysql_servers table in ProxySQL. It performs a read-only query to list existing backend server configurations, returning metadata about hostgroups, hostnames, ports, status, and weights. There is no capability to modify, delete, or execute operations—only to query and display data.

From the tool's definition Tool name 'proxysql_servers' and description 'List configured backend MySQL servers... Shows hostgroup, hostname, port, status, and weights' indicate a query/retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proxysql_servers 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_servers, this is the rule to start with:

proxysql_servers Allowed

proxysql_servers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "proxysql_servers": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every proxysql_servers call is checked against it from then on.

FAQ

Questions about proxysql_servers

What does the proxysql_servers tool do? +

List configured backend MySQL servers from mysql_servers table. Shows hostgroup, hostname, port, status, and weights. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on proxysql_servers? +

Register the Mysql MCP server in PolicyLayer and add a rule for proxysql_servers: 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.

What risk level is proxysql_servers? +

proxysql_servers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit proxysql_servers? +

Yes. Add a rate_limit block to the proxysql_servers 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.

How do I block proxysql_servers completely? +

Set action: deny in the PolicyLayer policy for proxysql_servers. 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.

What MCP server provides proxysql_servers? +

proxysql_servers 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.

KEEP EXPLORING

More on Mysql, and thousands of servers like it.

This server

All 223 Mysql tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →