mysql_execute · Multi-Database MCP Server MCP: Risk & Policy

WHAT IT DOES

What mysql_execute does on Multi-Database MCP Server

AI agents invoke mysql_execute to trigger actions in Multi-Database MCP Server. 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 mysql_execute needs a policy

While the tool can perform reversible writes (INSERT, UPDATE), it also explicitly permits DELETE and DDL operations that are irreversible. However, the primary classification is Execute because the tool's core function is to execute arbitrary SQL queries with those capabilities, rather than being restricted to one specific action.

From the tool's definition Tool description states 'Execute an INSERT, UPDATE, DELETE, or DDL query (requires FULL mode)'. INSERT/UPDATE modify data reversibly, DELETE removes data irreversibly, and DDL can alter schema.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mysql_execute Rate-limited

mysql_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": {
    "mysql_execute": {
      "limits": [
        {
          "counter": "mysql_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 Multi-Database MCP Server, so you can run agents against it safely.

FAQ

Questions about mysql_execute

What does the mysql_execute tool do? +

Execute an INSERT, UPDATE, DELETE, or DDL query (requires FULL mode). It is categorised as a Execute tool in the Multi-Database MCP Server 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_execute? +

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

What risk level is mysql_execute? +

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

Can I rate-limit mysql_execute? +

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

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

mysql_execute is provided by the Multi-Database MCP Server MCP server (nam088/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.