mysql_sys_schema_stats
Get aggregated statistics for a schema including tables, indexes, and auto-increment status.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-sys-schema-stats.md
What mysql_sys_schema_stats does on Mysql Mcp
AI agents call mysql_sys_schema_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.
Why mysql_sys_schema_stats is rated Low
This tool performs read-only queries against MySQL system tables to report statistics. It has no side effects, does not execute arbitrary code, does not modify data, and does not delete anything. It is purely informational, similar to SHOW or DESCRIBE statements in SQL. The blast radius of misuse is minimal since the agent can only retrieve existing metadata.
From the tool's definition Tool name and description indicate 'Get aggregated statistics' — a retrieval operation with no modification, creation, or deletion of data. It queries schema metadata (tables, indexes, auto-increment status) non-destructively.
Attacks that exploit this kind of access
The rule that runs mysql_sys_schema_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_sys_schema_stats, this is the rule to start with:
mysql_sys_schema_stats 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_sys_schema_stats call is checked against it from then on.
Questions about mysql_sys_schema_stats
Get aggregated statistics for a schema including tables, indexes, and auto-increment status. 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_sys_schema_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.
mysql_sys_schema_stats 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_sys_schema_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.
Set action: deny in the PolicyLayer policy for mysql_sys_schema_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.
mysql_sys_schema_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.
More on Mysql, and thousands of servers like it.
This server
Across the catalogue