mysql_query_cache_performance
Analyze query cache hit ratio and efficiency metrics.
This record as markdown: /tools/mukul975-mysql-mcp-server/mysql-query-cache-performance.md
What mysql_query_cache_performance does on Mysql
AI agents call mysql_query_cache_performance to retrieve information from Mysql 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_performance is rated Low
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.
Attacks that exploit this kind of access
The rule that runs mysql_query_cache_performance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_query_cache_performance, this is the rule to start with:
mysql_query_cache_performance 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 Mysql, apply this rule, and every mysql_query_cache_performance call is checked against it from then on.
Questions about mysql_query_cache_performance
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.
More on Mysql, and thousands of servers like it.
This server
Across the catalogue