mysql_reset_query_cache
Reset (clear) the query cache.
This record as markdown: /tools/mukul975-mcp-windows-automation/mysql-reset-query-cache.md
What mysql_reset_query_cache does on Mcp Windows
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.
Why mysql_reset_query_cache is rated Critical
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
Attacks that exploit this kind of access
The rule that runs mysql_reset_query_cache 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_reset_query_cache, this is the rule to start with:
mysql_reset_query_cache is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Windows, apply this rule, and every mysql_reset_query_cache call is checked against it from then on.
Questions about mysql_reset_query_cache
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.
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.
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.
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.
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.
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.
More on Mcp Windows, and thousands of servers like it.
Across the catalogue