proxysql_query_digest

Get query digest statistics showing top queries by execution count. Useful for identifying queries for routing, rewriting, or caching.

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/proxysql-query-digest.md

WHAT IT DOES

What proxysql_query_digest does on Mysql Mcp

AI agents call proxysql_query_digest 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 proxysql_query_digest is rated Low

This is a read-only diagnostic tool that queries ProxySQL's digest statistics to analyze query patterns. It has no side effects, does not execute user queries, and does not create, modify, or delete data. The mention of 'useful for identifying queries for routing, rewriting, or caching' describes potential use cases but does not alter what the tool actually does—retrieve statistics.

From the tool's definition Tool description states 'Get query digest statistics' and 'showing top queries by execution count' — it retrieves and displays aggregated query performance metrics without modifying data or executing arbitrary queries.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proxysql_query_digest 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_digest, this is the rule to start with:

proxysql_query_digest Allowed

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

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

FAQ

Questions about proxysql_query_digest

What does the proxysql_query_digest tool do? +

Get query digest statistics showing top queries by execution count. Useful for identifying queries for routing, rewriting, or caching. 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 proxysql_query_digest? +

Register the Mysql MCP server in PolicyLayer and add a rule for proxysql_query_digest: 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 proxysql_query_digest? +

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

Can I rate-limit proxysql_query_digest? +

Yes. Add a rate_limit block to the proxysql_query_digest 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 proxysql_query_digest completely? +

Set action: deny in the PolicyLayer policy for proxysql_query_digest. 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 proxysql_query_digest? +

proxysql_query_digest 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 →