mysqlsh_version
Get MySQL Shell version and installation status. Useful for verifying MySQL Shell is available before running other shell tools.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysqlsh-version.md
What mysqlsh_version does on Mysql Mcp
AI agents call mysqlsh_version 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_version is rated Low
This is a simple diagnostic/informational query that retrieves the version and status of MySQL Shell. It performs no modifications, deletions, code execution, or financial operations. It is purely read-only metadata retrieval, making it a Read category tool with low severity.
From the tool's definition Tool name and description indicate it 'Get[s] MySQL Shell version and installation status' — a query operation with no side effects, returning version/availability information only.
Attacks that exploit this kind of access
The rule that runs mysqlsh_version 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_version, this is the rule to start with:
mysqlsh_version 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_version call is checked against it from then on.
Questions about mysqlsh_version
Get MySQL Shell version and installation status. Useful for verifying MySQL Shell is available before running other shell tools. 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_version: 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_version 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_version 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_version. 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_version 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