mysql_show_warnings
Show MySQL warnings from the last statement.
This record as markdown: /tools/mukul975-mysql-mcp-server/mysql-show-warnings.md
What mysql_show_warnings does on Mysql
AI agents call mysql_show_warnings 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_warnings is rated Low
This tool retrieves and displays warning messages generated by the MySQL server from the prior executed statement. It is a read-only diagnostic operation that queries existing state without modifying, executing code, deleting data, or affecting system behavior. The blast radius is minimal—incorrect usage would simply return irrelevant warnings or no output.
From the tool's definition Tool name 'mysql_show_warnings' and description 'Show MySQL warnings from the last statement' indicate retrieval of diagnostic/metadata information with no side effects.
Attacks that exploit this kind of access
The rule that runs mysql_show_warnings 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_warnings, this is the rule to start with:
mysql_show_warnings 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_warnings call is checked against it from then on.
Questions about mysql_show_warnings
Show MySQL warnings from the last statement. 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_warnings: 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_warnings 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_warnings 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_warnings. 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_warnings 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