mysql_query_stats
Get top query statistics from performance_schema. NOTE: This returns overall server query stats. Do NOT pass a specific query or sql string.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-query-stats.md
What mysql_query_stats does on Mysql Mcp
AI agents call mysql_query_stats 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 mysql_query_stats is rated Low
The tool retrieves and returns aggregate query performance statistics from MySQL's built-in performance_schema database. It does not execute arbitrary SQL, modify data, delete anything, or move money. The explicit restriction against passing query strings confirms it performs read-only introspection. The blast radius of misuse is minimal—an agent could retrieve performance data but cannot alter system state.
From the tool's definition Tool description states 'Get top query statistics from performance_schema' and explicitly prohibits passing specific query or SQL strings.
Attacks that exploit this kind of access
The rule that runs mysql_query_stats 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 mysql_query_stats, this is the rule to start with:
mysql_query_stats 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 mysql_query_stats call is checked against it from then on.
Questions about mysql_query_stats
Get top query statistics from performance_schema. NOTE: This returns overall server query stats. Do NOT pass a specific query or sql string. 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 mysql_query_stats: 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.
mysql_query_stats 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 mysql_query_stats 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 mysql_query_stats. 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.
mysql_query_stats 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