mysqlsh_check_upgrade
Check MySQL server upgrade compatibility using util.checkForServerUpgrade(). Identifies potential issues before upgrading to a newer MySQL version.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysqlsh-check-upgrade.md
What mysqlsh_check_upgrade does on Mysql Mcp
AI agents call mysqlsh_check_upgrade to retrieve information from Mysql Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mysqlsh_check_upgrade is rated Low
The tool performs a diagnostic analysis of the MySQL server to identify upgrade compatibility issues. It reads configuration and server state to produce a report, with no side effects, data modifications, or command execution. This is a pure information-gathering operation typical of Read category tools (like 'check' or 'diagnose').
From the tool's definition Tool description states it "Identifies potential issues before upgrading" using a diagnostic utility method (util.checkForServerUpgrade()). This is a compatibility check that retrieves and analyzes server state without modifying data or executing commands.
Attacks that exploit this kind of access
The rule that runs mysqlsh_check_upgrade safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysqlsh_check_upgrade, this is the rule to start with:
mysqlsh_check_upgrade 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 Mcp, apply this rule, and every mysqlsh_check_upgrade call is checked against it from then on.
Questions about mysqlsh_check_upgrade
Check MySQL server upgrade compatibility using util.checkForServerUpgrade(). Identifies potential issues before upgrading to a newer MySQL version. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysqlsh_check_upgrade: 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. Nothing to install.
mysqlsh_check_upgrade 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 mysqlsh_check_upgrade 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 mysqlsh_check_upgrade. 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.
mysqlsh_check_upgrade is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). 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