mysqlsh_dump_tables
Dump specific tables using util.dumpTables(). Creates a compressed, parallel dump of specified tables from a schema.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysqlsh-dump-tables.md
What mysqlsh_dump_tables does on Mysql Mcp
AI agents call mysqlsh_dump_tables 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_tables is rated Low
This tool exports table data for backup or analysis purposes. While it accesses data, it does not modify, delete, or execute arbitrary code. The operation is read-only and leaves the database state unchanged. Severity is low because data export carries minimal risk compared to tools that modify or destroy data. Confidence is high because the description is explicit about the read-only nature of the dump operation.
From the tool's definition Tool description states it 'Creates a compressed, parallel dump of specified tables' using util.dumpTables(). Dumping is a read-only export operation that retrieves and serializes data without modifying or deleting it.
Attacks that exploit this kind of access
The rule that runs mysqlsh_dump_tables 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_tables, this is the rule to start with:
mysqlsh_dump_tables 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_tables call is checked against it from then on.
Questions about mysqlsh_dump_tables
Dump specific tables using util.dumpTables(). Creates a compressed, parallel dump of specified tables from a schema. 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_tables: 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_tables 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_tables 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_tables. 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_tables 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