mysql_column_stats

THE RISK

Low Risk

Why mysql_column_stats needs a policy

This tool queries metadata and statistical information about database columns. It returns analytical data without side effects, altering schema, executing code, or modifying data. It is a read operation that gathers information for analysis purposes.

From the tool's definition Tool retrieves 'column statistics and data distribution' with no mention of modification, deletion, or execution capabilities. The server is described as providing 'read-only queries' and 'performance analysis.'

Documented attack patterns abuse exactly the kind of access mysql_column_stats gives an agent:

POLICY

How to control mysql_column_stats

PolicyLayer is an MCP gateway — it sits between your AI agents and Mysql, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_column_stats:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_column_stats": {}
  }
}

mysql_column_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Mysql — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mysql tools

Destructive drop_event Drop a scheduled event. Destructive drop_partition Drop a partition from a table. Destructive drop_role Drop a role (MySQL 8.0+). Destructive drop_stored_function Drop a stored function. Destructive drop_stored_procedure Drop a stored procedure. Destructive mysql_delete_data Delete data from a table. Destructive mysql_drop_database Drop a MySQL database (USE WITH CAUTION!). Destructive mysql_drop_foreign_key Drop a foreign key constraint from a table.

All 233 Mysql tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about mysql_column_stats

What does the mysql_column_stats tool do? +

Get column statistics and data distribution. It is categorised as a Read tool in the Mysql MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_column_stats? +

Register the Mysql MCP server in PolicyLayer and add a rule for mysql_column_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. Nothing to install.

What risk level is mysql_column_stats? +

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

Can I rate-limit mysql_column_stats? +

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

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

mysql_column_stats is provided by the Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mysql tool call.

Start from Mysql, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →