mysql-query

Executes a MySQL query and returns structured tabular output.

SERVERDocker SOURCE@paretools/docker

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-docker/mysql-query.md

WHAT IT DOES

What mysql-query does on Docker

AI agents invoke mysql-query to trigger actions in Docker. 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.

RISK

Why mysql-query is rated High

Executing arbitrary SQL queries can include SELECT (Read), INSERT/UPDATE (Write), DELETE/DROP (Destructive), or stored procedure calls (Execute). Since the tool description says 'executes a MySQL query' without restricting the query type, it must be classified at the most severe plausible category. Arbitrary SQL execution can cause irreversible data loss (DROP, DELETE) or exfiltrate sensitive data.

From the tool's definition 'Executes a MySQL query' — the tool runs arbitrary SQL queries against a MySQL database

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql-query safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql-query, this is the rule to start with:

mysql-query Rate-limited

mysql-query 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql-query": {
      "limits": [
        {
          "counter": "mysql-query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docker, apply this rule, and every mysql-query call is checked against it from then on.

FAQ

Questions about mysql-query

What does the mysql-query tool do? +

Executes a MySQL query and returns structured tabular output. It is categorised as a Execute tool in the Docker MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mysql-query? +

Register the Docker MCP server in PolicyLayer and add a rule for mysql-query: 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 Docker. Nothing to install.

What risk level is mysql-query? +

mysql-query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mysql-query? +

Yes. Add a rate_limit block to the mysql-query 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.

How do I block mysql-query completely? +

Set action: deny in the PolicyLayer policy for mysql-query. 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.

What MCP server provides mysql-query? +

mysql-query is provided by the Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Docker, and thousands of servers like it.

This server

All 202 Docker tools → High-risk tools on this server →

Across the catalogue

aroflo_query_zone on AroFlo MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →