mysqlsh_dump_instance
Dump entire MySQL instance using util.dumpInstance(). Creates a compressed, parallel dump of all schemas (excluding system schemas). Ideal for full backups and migrations.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysqlsh-dump-instance.md
What mysqlsh_dump_instance does on Mysql Mcp
AI agents call mysqlsh_dump_instance 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_dump_instance is rated Low
This tool reads and exports data from the entire MySQL instance into a dump file. It does not modify, delete, or execute arbitrary data changes — it's a backup/export operation. However, severity is high because it reads ALL schemas across the entire instance, representing a massive data exfiltration risk if misused.
From the tool's definition 'Dump entire MySQL instance using util.dumpInstance()' and 'Creates a compressed, parallel dump of all schemas'
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs mysqlsh_dump_instance 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_dump_instance, this is the rule to start with:
mysqlsh_dump_instance 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_dump_instance call is checked against it from then on.
Questions about mysqlsh_dump_instance
Dump entire MySQL instance using util.dumpInstance(). Creates a compressed, parallel dump of all schemas (excluding system schemas). Ideal for full backups and migrations. 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_dump_instance: 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_dump_instance 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_dump_instance 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_dump_instance. 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_dump_instance 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