mysql_stats_row_number
Assign sequential row numbers within an ordered result set. Use partitionBy to restart numbering per group.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-stats-row-number.md
What mysql_stats_row_number does on Mysql Mcp
AI agents invoke mysql_stats_row_number to trigger actions in Mysql Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why mysql_stats_row_number is rated High
The tool executes SQL window functions to transform and assign row numbers to result sets with partitioning logic. While it does not delete or create permanent schema objects, it executes non-trivial database operations whose effects depend on the query arguments (partitionBy clause, ordering).
From the tool's definition Tool name includes 'stats' and description states 'Assign sequential row numbers within an ordered result set...Use partitionBy' — this performs window function operations (ROW_NUMBER) that modify query result sets and execute within the database context.
Attacks that exploit this kind of access
The rule that runs mysql_stats_row_number 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_row_number, this is the rule to start with:
mysql_stats_row_number stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_row_number call is checked against it from then on.
Questions about mysql_stats_row_number
Assign sequential row numbers within an ordered result set. Use partitionBy to restart numbering per group. It is categorised as a Execute tool in the Mysql Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_stats_row_number: 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_row_number is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mysql_stats_row_number 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_row_number. 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_row_number 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