Provide real-time metrics on query performance and bottlenecks.
AI agents call mysql_real_time_query_perf_metrics to retrieve information from Mcp Windows 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 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…
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 Mcp Windows, 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 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.
Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.