proxysql_users
List configured MySQL users from mysql_users table. Shows username, active status, default hostgroup, and connection limits. Passwords are redacted.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/proxysql-users.md
What proxysql_users does on Mysql Mcp
AI agents call proxysql_users 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_users is rated Low
This tool retrieves and displays user account information from the mysql_users table in ProxySQL. It performs a passive query with no side effects, no code execution, no destructive operations, and no financial impact. The redaction of passwords further demonstrates read-only intent. While user information can be sensitive, the tool itself is purely informational and does not modify, delete, or execute anything.
From the tool's definition Tool 'proxysql_users' explicitly 'lists' configured MySQL users and 'shows' user attributes. The description states 'passwords are redacted', confirming this is a read-only query operation with no data modification capability.
Attacks that exploit this kind of access
The rule that runs proxysql_users 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_users, this is the rule to start with:
proxysql_users 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_users call is checked against it from then on.
Questions about proxysql_users
List configured MySQL users from mysql_users table. Shows username, active status, default hostgroup, and connection limits. Passwords are redacted. 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_users: 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_users 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_users 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_users. 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_users 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