mysql_real_time_query_perf_metrics
Provide real-time metrics on query performance and bottlenecks.
This record as markdown: /tools/mukul975-mcp-windows-automation/mysql-real-time-query-perf-metrics.md
What mysql_real_time_query_perf_metrics does on Mcp Windows
AI agents call mysql_real_time_query_perf_metrics to retrieve information from Mcp Windows 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 metrics from MySQL queries. It queries existing data to analyze performance characteristics but does not modify, execute arbitrary queries, delete data, or trigger financial transactions. It is purely observational/diagnostic in nature, fitting the Read category. Severity is low because metric retrieval has minimal blast radius even if misused.
From the tool's definition Tool name and description indicate it 'Provide[s] real-time metrics on query performance and bottlenecks.' The verb 'provide' and the focus on metrics gathering and analysis describe retrieval and monitoring of data with no modifications, deletions, or code…
Attacks that exploit this kind of access
The rule that runs mysql_real_time_query_perf_metrics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, 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:
mysql_real_time_query_perf_metrics 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 Mcp Windows, apply this rule, and every mysql_real_time_query_perf_metrics call is checked against it from then on.
Questions about mysql_real_time_query_perf_metrics
Provide real-time metrics on query performance and bottlenecks. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.
Register the Mcp Windows 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 Mcp Windows. 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 Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Windows, and thousands of servers like it.
This server
Across the catalogue