执行 MySQL UPDATE 更新操作。若服务启动时已预配置 MySQL，会直接使用默认连接。
AI agents use mysql_update to create or update resources in Db — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Db environment.
The tool modifies existing database records, which is a Write operation. It is not Destructive because UPDATE is reversible (the old values can be restored with another UPDATE). Severity is medium because misuse could corrupt data integrity or expose sensitive information through careless updates, but the operation can theoretically be rolled back.
From the tool's definition Tool name 'mysql_update' and description '执行 MySQL UPDATE 更新操作' (execute MySQL UPDATE operation) directly indicates data modification. UPDATE is a reversible write operation that modifies existing data without deletion.
Documented attack patterns abuse exactly the kind of access mysql_update 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_update:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_update": {
"limits": [
{
"counter": "mysql_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mysql_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
执行 MySQL UPDATE 更新操作。若服务启动时已预配置 MySQL，会直接使用默认连接。. It is categorised as a Write tool in the Db MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Db MCP server in PolicyLayer and add a rule for mysql_update: 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_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mysql_update 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_update. 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_update 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.