proxysql_query_rules
List query routing rules from mysql_query_rules table. Shows rule IDs, match patterns, destination hostgroups, and cache settings.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/proxysql-query-rules.md
What proxysql_query_rules does on Mysql Mcp
AI agents call proxysql_query_rules 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_query_rules is rated Low
The tool performs a read-only query against the mysql_query_rules table to display ProxySQL routing configuration. It retrieves and presents existing data without modifying, deleting, or executing anything. This is a low-severity informational query suitable for auditing or understanding routing behavior.
From the tool's definition Tool description states 'List query routing rules' with 'Shows rule IDs, match patterns, destination hostgroups, and cache settings' — indicative of a retrieval/inspection operation with no side effects.
Attacks that exploit this kind of access
The rule that runs proxysql_query_rules 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_query_rules, this is the rule to start with:
proxysql_query_rules 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_query_rules call is checked against it from then on.
Questions about proxysql_query_rules
List query routing rules from mysql_query_rules table. Shows rule IDs, match patterns, destination hostgroups, and cache settings. 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_query_rules: 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_query_rules 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_query_rules 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_query_rules. 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_query_rules 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