Critical Risk →

mysql_reset_query_cache

Reset (clear) the query cache.

How to control mysql_reset_query_cache ↓

AI agents call mysql_reset_query_cache to permanently remove resources in Mcp Windows — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Clearing/resetting the query cache is an irreversible destructive action — all cached query results are permanently purged. While the cache will eventually repopulate, the act of clearing it cannot be undone and can have significant performance impact on a production MySQL system by forcing all queries to re-execute against the database.

From the tool's definition Reset (clear) the query cache

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "mysql_reset_query_cache"
  ]
}

mysql_reset_query_cache disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  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.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the mysql_reset_query_cache tool do? +

Reset (clear) the query cache. It is categorised as a Destructive tool in the Mcp Windows MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on mysql_reset_query_cache? +

Register the Mcp Windows MCP server in PolicyLayer and add a rule for mysql_reset_query_cache: 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_reset_query_cache? +

mysql_reset_query_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit mysql_reset_query_cache? +

Yes. Add a rate_limit block to the mysql_reset_query_cache 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_reset_query_cache completely? +

Set action: deny in the PolicyLayer policy for mysql_reset_query_cache. 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_reset_query_cache? +

mysql_reset_query_cache 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.