Low Risk

mysql_query_cache_stats

Show query cache statistics.

How to control mysql_query_cache_stats ↓

AI agents call mysql_query_cache_stats 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.

Low Risk

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.

Documented attack patterns abuse exactly the kind of access mysql_query_cache_stats 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_query_cache_stats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_query_cache_stats": {}
  }
}

mysql_query_cache_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Windows — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the mysql_query_cache_stats tool do? +

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.

How do I enforce a policy on mysql_query_cache_stats? +

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.

What risk level is mysql_query_cache_stats? +

mysql_query_cache_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mysql_query_cache_stats? +

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.

How do I block mysql_query_cache_stats completely? +

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.

What MCP server provides mysql_query_cache_stats? +

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.

Enforce policy on every Mcp Windows tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.