mysql_show_error_log
Read the MySQL error log file content. (Requires file access privileges)
This record as markdown: /tools/mukul975-mysql-mcp-server/mysql-show-error-log.md
What mysql_show_error_log does on Mysql
AI agents call mysql_show_error_log 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_show_error_log is rated Low
This is a read operation that retrieves error log information from the MySQL server. While it doesn't modify data, the severity is elevated to medium because error logs can contain sensitive information (credentials, internal system details, database schema hints) that could be exploited if an AI agent misuses access.
From the tool's definition Tool name contains 'show' and description explicitly states 'Read the MySQL error log file content.' It retrieves log data without modification.
Attacks that exploit this kind of access
The rule that runs mysql_show_error_log 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_show_error_log, this is the rule to start with:
mysql_show_error_log 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_show_error_log call is checked against it from then on.
Questions about mysql_show_error_log
Read the MySQL error log file content. (Requires file access privileges). 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_show_error_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. Nothing to install.
mysql_show_error_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 mysql_show_error_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 mysql_show_error_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.
mysql_show_error_log 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