Updates a MySQL database configuration in Dokploy.
AI agents use mysql-update to create or update resources in Dokploy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dokploy MCP Server environment.
This tool modifies database configuration settings, which is a reversible write operation. It is categorized as 'Write' rather than 'Destructive' because updates are typically reversible. Severity is 'high' because misconfiguration of a MySQL database could cause service disruptions, data integrity issues, or expose sensitive database credentials if configurations are altered incorrectly.
From the tool's definition Tool name 'mysql-update' and description 'Updates a MySQL database configuration in Dokploy' indicate modification of database configuration settings.
Attacks that exploit this kind of access
Updates a MySQL database configuration in Dokploy. It is categorised as a Write tool in the Dokploy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dokploy MCP Server 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 Dokploy MCP Server. 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 Dokploy MCP Server MCP server (limehawk/dokploy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →