The GenAI/MCP `run sql readonly` tool violates its read-only contract for MySQL targets. The tool validates input using a substring blacklist and a first-keyword allowlist, but executes the SQL string on a backend connection created with `CLIENT MULTI STATEMENTS`. This allows a caller to bypass restrictions by submitting a read-only first statement followed by a side-effecting second statement, such as `SELECT 1; RENAME TABLE ...`. The validator accepts these payloads because they start with `SELECT` and certain side-effecting statements like `RENAME TABLE`, `SET`, `RESET`, `LOCK TABLES`, and `KILL` are not included in the blacklist. This issue was observed at the '/mcp/query' endpoint, enabling an MCP caller to perform backend writes or administrative SQL based on the target account's privileges.