执行MySQL查询并返回结果 Args: query: SQL查询语句 params: 查询参数 (可选) Returns: 查询结果的JSON字符串
AI agents invoke mysql_query 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.
This tool executes arbitrary SQL queries against a MySQL database. While the name suggests read operations (query), it accepts any SQL statement, meaning an agent could run INSERT, UPDATE, DELETE, DROP, or other destructive/modifying commands.
From the tool's definition 执行MySQL查询并返回结果 / query: SQL查询语句 — accepts arbitrary SQL statements for execution
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 MySQL MCP Server, 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查询并返回结果 Args: query: SQL查询语句 params: 查询参数 (可选) Returns: 查询结果的JSON字符串. 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 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 MySQL MCP Server. 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 MySQL MCP Server MCP server (mangooer/mysql-mcp-server-sse). 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.
12 MySQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.