mysql_stats_running_total

Calculate cumulative running total (SUM OVER) for a numeric column. Use partitionBy to reset total per group.

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

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

What mysql_stats_running_total does on Mysql Mcp

AI agents call mysql_stats_running_total 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_running_total is rated Low

This tool performs a read-only analytical computation (window function SUM OVER) on existing data. It queries and aggregates data without modifying, deleting, or executing arbitrary code. The partitionBy parameter is a grouping hint for the calculation, not a side-effecting operation.

From the tool's definition Calculate cumulative running total (SUM OVER) for a numeric column

Questions about mysql_stats_running_total

What does the mysql_stats_running_total tool do? +

Calculate cumulative running total (SUM OVER) for a numeric column. Use partitionBy to reset total per group. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_stats_running_total? +

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

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

Can I rate-limit mysql_stats_running_total? +

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

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

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