mysql_stats_descriptive
Calculate descriptive statistics (mean, median, stddev, min, max, count) for a numeric column.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-stats-descriptive.md
What mysql_stats_descriptive does on Mysql Mcp
AI agents call mysql_stats_descriptive 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_stats_descriptive is rated Low
This tool reads data from a numeric column and returns statistical summaries. It has no side effects, does not modify or delete data, and does not execute arbitrary code. It is a straightforward analytical query operation, fitting the Read category with low severity since misuse would only expose data already readable to the agent.
From the tool's definition Tool performs 'Calculate descriptive statistics (mean, median, stddev, min, max, count)' — a query operation that retrieves and computes aggregate metrics from data without modifying, deleting, or executing arbitrary operations.
Attacks that exploit this kind of access
The rule that runs mysql_stats_descriptive 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_stats_descriptive, this is the rule to start with:
mysql_stats_descriptive 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_stats_descriptive call is checked against it from then on.
Questions about mysql_stats_descriptive
Calculate descriptive statistics (mean, median, stddev, min, max, count) for a numeric column. 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_stats_descriptive: 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_stats_descriptive 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_stats_descriptive 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_stats_descriptive. 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_stats_descriptive 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