Provide real-time metrics on query performance and bottlenecks.
AI agents call mysql_real_time_query_perf_metrics to retrieve information from Mysql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access mysql_real_time_query_perf_metrics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mysql, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_real_time_query_perf_metrics:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_real_time_query_perf_metrics": {}
}
}mysql_real_time_query_perf_metrics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Provide real-time metrics on query performance and bottlenecks. It is categorised as a Read tool in the Mysql MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_real_time_query_perf_metrics: 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. Nothing to install.
mysql_real_time_query_perf_metrics 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_real_time_query_perf_metrics 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_real_time_query_perf_metrics. 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_real_time_query_perf_metrics is provided by the Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mysql, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
233 Mysql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.