mysql_real_time_query_perf_metrics

What mysql_real_time_query_perf_metrics does on Mysql

AI agents call mysql_real_time_query_perf_metrics to retrieve information from Mysql without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why mysql_real_time_query_perf_metrics is rated Low

This tool retrieves and reports performance data about existing queries. It reads metrics without creating, modifying, deleting, or executing any database operations. The sibling tools include destructive operations (drop_event, alter_event, create_user_with_ssl), but this specific tool is explicitly for analysis and monitoring only. The 'read-only' claim in the server description aligns with this classification.

From the tool's definition Tool name includes 'metrics' and description states 'Provide real-time metrics on query performance and bottlenecks' — clearly a monitoring/retrieval function with no modification, deletion, or execution of arbitrary code.

The rule that runs mysql_real_time_query_perf_metrics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_real_time_query_perf_metrics, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_real_time_query_perf_metrics": {}
  }
}

Questions about mysql_real_time_query_perf_metrics