proxysql_global_variables
Get ProxySQL global variables. Filter by prefix: mysql (MySQL proxy settings), admin (admin interface settings), or all. Use like parameter for pattern matching.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/proxysql-global-variables.md
What proxysql_global_variables does on Mysql Mcp
AI agents call proxysql_global_variables 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_global_variables is rated Low
This tool queries configuration or state information from ProxySQL without modifying, deleting, or executing operations. Even though ProxySQL controls MySQL proxy behavior, merely reading its global variables (mysql settings, admin settings) has no side effects and poses minimal risk. The worst case would be information disclosure of proxy configuration details, which is a low-severity risk.
From the tool's definition Tool retrieves ProxySQL global variables with filtering and pattern matching; no modification, deletion, or execution capabilities mentioned. The description explicitly states 'Get' variables, which is a read operation.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs proxysql_global_variables 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_global_variables, this is the rule to start with:
proxysql_global_variables 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_global_variables call is checked against it from then on.
Questions about proxysql_global_variables
Get ProxySQL global variables. Filter by prefix: mysql (MySQL proxy settings), admin (admin interface settings), or all. Use like parameter for pattern matching. 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_global_variables: 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_global_variables 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_global_variables 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_global_variables. 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_global_variables 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