慢查询相关变量（slow_query%、long_query%）
AI agents call slow_query_status to retrieve information from MySQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic information about slow query settings and metrics. It has no side effects, does not modify data, does not execute arbitrary queries, and does not delete anything. It is a simple status inspection tool that returns configuration or performance metrics.
From the tool's definition Tool name 'slow_query_status' and description indicating it retrieves slow query variables (slow_query%, long_query%) — these are read-only status/diagnostic metrics from MySQL.
Attacks that exploit this kind of access
慢查询相关变量（slow_query%、long_query%）. It is categorised as a Read tool in the MySQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for slow_query_status: 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 MCP Server. Nothing to install.
slow_query_status 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 slow_query_status 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 slow_query_status. 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.
slow_query_status is provided by the MySQL MCP Server MCP server (yclenove/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →