mysqlsh_run_script
Execute a JavaScript, Python, or SQL script via MySQL Shell. Provides access to X DevAPI, AdminAPI, and all MySQL Shell features.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysqlsh-run-script.md
What mysqlsh_run_script does on Mysql Mcp
AI agents invoke mysqlsh_run_script to trigger actions in Mysql Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why mysqlsh_run_script is rated High
This tool directly executes arbitrary scripts in multiple languages and provides unrestricted access to MySQL Shell administrative features. An AI agent could use this to execute malicious code, modify database structure, trigger stored procedures, or perform unintended administrative operations. While it could theoretically be used destructively, the primary risk is uncontrolled code execution.
From the tool's definition Tool description states 'Execute a JavaScript, Python, or SQL script via MySQL Shell. Provides access to X DevAPI, AdminAPI, and all MySQL Shell features.' The term 'Execute' combined with support for arbitrary code (JavaScript, Python, SQL) and access to…
Attacks that exploit this kind of access
The rule that runs mysqlsh_run_script 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_run_script, this is the rule to start with:
mysqlsh_run_script stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_run_script call is checked against it from then on.
Questions about mysqlsh_run_script
Execute a JavaScript, Python, or SQL script via MySQL Shell. Provides access to X DevAPI, AdminAPI, and all MySQL Shell features. It is categorised as a Execute tool in the Mysql Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mysql MCP server in PolicyLayer and add a rule for mysqlsh_run_script: 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_run_script is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mysqlsh_run_script 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_run_script. 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_run_script 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.
Across the catalogue