读取 MYSQL_MCP_SLOW_LOG_PATH 慢日志文件尾部（默认 ${AUDIT_TAIL_DEFAULT} 行，最大 ${AUDIT_TAIL_MAX}）
AI agents call read_slow_query_log 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 reads the MySQL slow query log file (tail operation with configurable line limits). It retrieves historical log data for inspection/monitoring purposes with no side effects. This is a pure Read operation—the lowest severity category. The confidence is high because the intent is clear despite the Chinese description, and log file access is a standard read-only audit function.
From the tool's definition Tool name and description indicate reading/tailing a log file: '读取...慢日志文件尾部' (read slow query log file tail). No modification, deletion, or execution of queries is performed—only retrieval of existing audit log data.
Attacks that exploit this kind of access
读取 MYSQL_MCP_SLOW_LOG_PATH 慢日志文件尾部（默认 ${AUDIT_TAIL_DEFAULT} 行，最大 ${AUDIT_TAIL_MAX}）. 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 read_slow_query_log: 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.
read_slow_query_log 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 read_slow_query_log 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 read_slow_query_log. 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.
read_slow_query_log 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 →