mysql_query_cache_stats
Show query cache statistics.
This record as markdown: /tools/mukul975-mcp-windows-automation/mysql-query-cache-stats.md
What mysql_query_cache_stats does on Mcp Windows
AI agents call mysql_query_cache_stats 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_query_cache_stats is rated Low
This tool queries and returns statistics about MySQL query caching—a read-only operation that retrieves system information with no side effects, data modification, or code execution. The low severity reflects minimal risk even if accessed by an unauthorized agent, as it only exposes performance telemetry.
From the tool's definition Tool name 'mysql_query_cache_stats' and description 'Show query cache statistics' indicate retrieval and display of existing performance metrics without modification or execution of code.
Attacks that exploit this kind of access
The rule that runs mysql_query_cache_stats 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_query_cache_stats, this is the rule to start with:
mysql_query_cache_stats 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_query_cache_stats call is checked against it from then on.
Questions about mysql_query_cache_stats
Show query cache statistics. 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_query_cache_stats: 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_query_cache_stats 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_query_cache_stats 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_query_cache_stats. 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_query_cache_stats 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