mysql_stats_moving_avg
Calculate moving average (AVG OVER sliding window) for a numeric column. Specify windowSize for the number of preceding rows to include.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-stats-moving-avg.md
What mysql_stats_moving_avg does on Mysql Mcp
AI agents call mysql_stats_moving_avg 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_moving_avg is rated Low
This tool retrieves and computes statistics on existing data using SQL window functions. It has no side effects: it does not create, modify, delete, or execute arbitrary code. The operation is read-only analysis of data, making it a Read category tool with low risk if misused by an agent.
From the tool's definition Tool performs 'Calculate moving average (AVG OVER sliding window) for a numeric column' — a pure aggregation query with no modification, deletion, or execution of external operations. Uses AVG window function typical of SELECT queries.
Attacks that exploit this kind of access
The rule that runs mysql_stats_moving_avg 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_moving_avg, this is the rule to start with:
mysql_stats_moving_avg 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_stats_moving_avg call is checked against it from then on.
Questions about mysql_stats_moving_avg
Calculate moving average (AVG OVER sliding window) for a numeric column. Specify windowSize for the number of preceding rows to include. 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_stats_moving_avg: 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_moving_avg 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_stats_moving_avg 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_moving_avg. 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_moving_avg 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