mysql_create_dump
Generate mysqldump command for backing up database.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-create-dump.md
What mysql_create_dump does on Mysql Mcp
AI agents invoke mysql_create_dump 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 mysql_create_dump is rated High
The tool triggers an external mysqldump process (shell command execution) against the database. While a dump is non-destructive to source data, it executes an OS-level command and can exfiltrate large volumes of sensitive data. This places it firmly in Execute, with high severity due to potential data exfiltration risk if misused.
From the tool's definition "Generate mysqldump command for backing up database" — the tool generates and presumably executes a mysqldump command, which is an external shell/CLI operation that runs against the database.
Attacks that exploit this kind of access
The rule that runs mysql_create_dump 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 mysql_create_dump, this is the rule to start with:
mysql_create_dump 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 mysql_create_dump call is checked against it from then on.
Questions about mysql_create_dump
Generate mysqldump command for backing up database. 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 mysql_create_dump: 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.
mysql_create_dump 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 mysql_create_dump 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 mysql_create_dump. 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.
mysql_create_dump 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