execute_query · MySQL Managing MCP: Risk & Policy

WHAT IT DOES

What execute_query does on MySQL Managing MCP

AI agents invoke execute_query to trigger actions in MySQL Managing 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 IT NEEDS A POLICY

Why execute_query needs a policy

While the tool could be used for read-only SELECT queries (Read category), it accepts 'General SQL query' with no stated restrictions, meaning a malicious or careless actor could pass destructive queries (DROP, DELETE, TRUNCATE) or write/modify queries (INSERT, UPDATE). The Execute category is appropriate because the blast radius depends heavily on the query argument and the permissions of the database user.

From the tool's definition Tool description states 'Execute a General SQL query' — the word 'Execute' combined with 'General SQL query' indicates the tool runs arbitrary SQL commands whose effects depend on the query arguments provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_query Rate-limited

execute_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": {
    "execute_query": {
      "limits": [
        {
          "counter": "execute_query_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 MySQL Managing MCP, so you can run agents against it safely.

FAQ

Questions about execute_query

What does the execute_query tool do? +

Execute a General SQL query. It is categorised as a Execute tool in the MySQL Managing MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_query? +

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

What risk level is execute_query? +

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

Can I rate-limit execute_query? +

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

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

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