mysql_sys_statement_summary
Get statement execution statistics including latency and row counts from sys schema.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-sys-statement-summary.md
What mysql_sys_statement_summary does on Mysql Mcp
AI agents call mysql_sys_statement_summary 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_statement_summary is rated Low
This tool retrieves performance statistics from the MySQL sys schema, a built-in performance_schema view. It performs only information retrieval with no side effects, data modification, or code execution. Even in an enterprise context where latency/row count data could inform decisions, the tool itself is purely diagnostic and read-only.
From the tool's definition Tool name contains 'summary' and description states 'Get statement execution statistics' with 'from sys schema'. The verbs 'get' and 'statistics' indicate read-only querying of existing diagnostic data.
Attacks that exploit this kind of access
The rule that runs mysql_sys_statement_summary 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_statement_summary, this is the rule to start with:
mysql_sys_statement_summary 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_statement_summary call is checked against it from then on.
Questions about mysql_sys_statement_summary
Get statement execution statistics including latency and row counts from sys schema. 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_statement_summary: 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_statement_summary 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_statement_summary 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_statement_summary. 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_statement_summary 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