AI agents invoke execute_sql to trigger actions in MySQL 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.
SQL query execution is categorized as Execute rather than Read, Write, or Destructive because the tool itself is argument-dependent—it can perform any of these actions based on what SQL is provided.
From the tool's definition Tool description states 'Execute a SQL query' which directly indicates code execution. Combined with server description 'execute SQL queries', this tool allows arbitrary SQL execution against MySQL databases.
Documented attack patterns abuse exactly the kind of access execute_sql gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MySQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_sql:
{
"version": "1",
"default": "deny",
"tools": {
"execute_sql": {
"limits": [
{
"counter": "execute_sql_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_sql 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.
Free to start. No card required.
Execute a SQL query. It is categorised as a Execute tool in the MySQL MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for execute_sql: 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 Server. Nothing to install.
execute_sql 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 execute_sql 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 execute_sql. 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.
execute_sql is provided by the MySQL MCP Server MCP server (leonmelamud/mysql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MySQL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MySQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.