mysqlsh_export_table
Export a MySQL table to a file using util.exportTable(). Supports CSV and TSV formats with WHERE clause filtering.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysqlsh-export-table.md
What mysqlsh_export_table does on Mysql Mcp
AI agents call mysqlsh_export_table 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_export_table is rated Low
This tool reads data from a MySQL table and writes it to a file. While it creates a file on disk (a Write side effect), its primary purpose is data extraction/export. However, writing to the filesystem could overwrite existing files and exposes potentially sensitive data, warranting medium severity. The dominant operation is reading from the database, but the file write side effect is non-trivial.
From the tool's definition Export a MySQL table to a file using util.exportTable(). Supports CSV and TSV formats with WHERE clause filtering.
Attacks that exploit this kind of access
The rule that runs mysqlsh_export_table 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_export_table, this is the rule to start with:
mysqlsh_export_table 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_export_table call is checked against it from then on.
Questions about mysqlsh_export_table
Export a MySQL table to a file using util.exportTable(). Supports CSV and TSV formats with WHERE clause filtering. 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_export_table: 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_export_table 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_export_table 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_export_table. 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_export_table 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