mysql_stats_histogram

View or update column histogram statistics (MySQL 8.0+).

SERVERMysql Mcp SOURCEoci:docker.io/writenotenow/mysql-mcp:v1.0.0
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-stats-histogram.md

What mysql_stats_histogram does on Mysql Mcp

AI agents use mysql_stats_histogram to create or update resources in Mysql Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mysql Mcp environment.

Why mysql_stats_histogram is rated Medium

While viewing statistics is a read operation, the explicit mention of 'update' capability means this tool can modify data. Histogram statistics are metadata used by the query optimizer; updating them is reversible and does not permanently delete data, so it falls under Write rather than Destructive.

From the tool's definition Tool description states it can 'View or update column histogram statistics'. The 'update' verb indicates this tool modifies database statistics metadata, which is a reversible write operation.

Questions about mysql_stats_histogram

What does the mysql_stats_histogram tool do? +

View or update column histogram statistics (MySQL 8.0+). It is categorised as a Write tool in the Mysql Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mysql_stats_histogram? +

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

mysql_stats_histogram is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mysql_stats_histogram? +

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

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

mysql_stats_histogram 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mysql's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.