Analyze query cache hit ratio and efficiency metrics.
AI agents call mysql_query_cache_performance to retrieve information from Mysql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs analysis and monitoring of query cache performance metrics. It retrieves performance data for inspection purposes only, with no capability to modify, delete, or execute arbitrary operations. The 'analyze' verb in this context refers to querying and interpreting existing metrics, not executing arbitrary SQL.
From the tool's definition Tool name and description indicate 'Analyze query cache hit ratio and efficiency metrics' — a read-only operation that retrieves and analyzes performance data without modifying database state.
Documented attack patterns abuse exactly the kind of access mysql_query_cache_performance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mysql, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_query_cache_performance:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_query_cache_performance": {}
}
}mysql_query_cache_performance 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.
Analyze query cache hit ratio and efficiency metrics. It is categorised as a Read tool in the Mysql MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_query_cache_performance: 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 Mysql. Nothing to install.
mysql_query_cache_performance 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_performance 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_performance. 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_performance is provided by the Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mysql, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
233 Mysql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.