mysql_query_stats

Get query statistics from performance_schema.

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/mysql-query-stats.md

WHAT IT DOES

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.

RISK

Why mysql_query_stats is rated Low

This tool queries performance statistics from MySQL's read-only performance_schema database. It retrieves metrics for analysis and monitoring purposes without creating, modifying, or deleting data. The blast radius of misuse is minimal—an agent could at most access query performance metadata that is already collected by MySQL for diagnostic purposes.

From the tool's definition Tool name 'mysql_query_stats' and description 'Get query statistics from performance_schema' indicate retrieval of monitoring/observability data from MySQL's built-in performance schema tables.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

mysql_query_stats 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": {
    "mysql_query_stats": {}
  }
}

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 mysql_query_stats call is checked against it from then on.

FAQ

Questions about mysql_query_stats

What does the mysql_query_stats tool do? +

Get query statistics from performance_schema. 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 mysql_query_stats? +

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.

What risk level is mysql_query_stats? +

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

Can I rate-limit mysql_query_stats? +

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.

How do I block mysql_query_stats completely? +

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.

What MCP server provides mysql_query_stats? +

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.

KEEP EXPLORING

More on Mysql, and thousands of servers like it.

This server

All 223 Mysql tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

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