读取 MCP_AUDIT_LOG 文件尾部（默认 ${AUDIT_TAIL_DEFAULT} 行，最大 ${AUDIT_TAIL_MAX}）
AI agents call read_audit_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 retrieves and queries audit log data without any side effects. It only reads historical log entries with bounded output, making it a Read operation. The lack of write, delete, or execute capabilities, combined with the read-only nature of audit logs, results in low severity. The server's broader support for write/delete operations does not apply to this specific tool.
From the tool's definition Tool name is 'read_audit_log' and description states it reads ('读取') the tail of MCP_AUDIT_LOG file with configurable line limits (default ${AUDIT_TAIL_DEFAULT}, max ${AUDIT_TAIL_MAX}). No modification, deletion, or execution capability.
Attacks that exploit this kind of access
读取 MCP_AUDIT_LOG 文件尾部（默认 ${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_audit_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_audit_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_audit_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_audit_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_audit_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 →