执行 MySQL SQL 语句（支持 SELECT、INSERT、UPDATE、DELETE 等所有 SQL 操作）。如果服务启动时已预配置 MySQL，本工具会直接复用默认连接，无需先调用 mysql_connect。
AI agents invoke mysql_query to trigger actions in Db. 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.
This tool executes arbitrary MySQL SQL statements including INSERT, UPDATE, and DELETE — and potentially DROP/TRUNCATE if not explicitly blocked. Because it supports all SQL operations, a misuse could lead to irreversible data destruction (Destructive) or large-scale data modification (Write). The most severe applicable category is Execute (with Destructive potential), given it runs arbitrary SQL.
From the tool's definition 执行 MySQL SQL 语句（支持 SELECT、INSERT、UPDATE、DELETE 等所有 SQL 操作）
Documented attack patterns abuse exactly the kind of access mysql_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Db, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_query:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_query": {
"limits": [
{
"counter": "mysql_query_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
执行 MySQL SQL 语句（支持 SELECT、INSERT、UPDATE、DELETE 等所有 SQL 操作）。如果服务启动时已预配置 MySQL，本工具会直接复用默认连接，无需先调用 mysql_connect。. It is categorised as a Execute tool in the Db MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Db 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 Db. Nothing to install.
mysql_query 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 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.
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.
mysql_query is provided by the Db MCP server (wannanbigpig/db-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Db, 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.
34 Db tools catalogued and risk-classified — across an index of 43,000+ MCP servers.