dry_run_execute · MCP Server MySQL MCP: Risk & Policy

WHAT IT DOES

What dry_run_execute does on MCP Server MySQL

AI agents invoke dry_run_execute to trigger actions in MCP Server MySQL. 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 IT NEEDS A POLICY

Why dry_run_execute needs a policy

This is classified as Execute rather than Write because it runs database commands whose effects (even if temporary) depend on the SQL arguments provided. The transaction rollback makes it non-destructive in outcome, but the execution itself—parsing and running INSERT/UPDATE/DELETE statements—is an active operation that could affect application state, trigger triggers, or consume resources.

From the tool's definition Tool description states it executes INSERT, UPDATE, or DELETE operations inside a transaction. These are DML (Data Manipulation Language) commands that modify data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dry_run_execute Rate-limited

dry_run_execute 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": {
    "dry_run_execute": {
      "limits": [
        {
          "counter": "dry_run_execute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Server MySQL, so you can run agents against it safely.

FAQ

Questions about dry_run_execute

What does the dry_run_execute tool do? +

Execute an INSERT, UPDATE, or DELETE inside a transaction and roll it back. It is categorised as a Execute tool in the MCP Server MySQL MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on dry_run_execute? +

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

What risk level is dry_run_execute? +

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

Can I rate-limit dry_run_execute? +

Yes. Add a rate_limit block to the dry_run_execute 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 dry_run_execute completely? +

Set action: deny in the PolicyLayer policy for dry_run_execute. 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 dry_run_execute? +

dry_run_execute is provided by the MCP Server MySQL MCP server (nilsir/mcp-server-mysql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.