Update an existing MySQL database instance
AI agents use update_mysql_instance to create or update resources in Linode MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linode MCP Server environment.
This tool modifies existing database configuration or state but does not delete or destroy the instance, making it a Write rather than Destructive action. However, it is classified as high severity because misuse could corrupt database settings, cause service disruption, or alter critical configurations that affect data availability and integrity across dependent applications.
From the tool's definition Update an existing MySQL database instance — performs modification of a database resource, which is a reversible write operation that can change configurations, settings, or other mutable state.
Documented attack patterns abuse exactly the kind of access update_mysql_instance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_mysql_instance:
{
"version": "1",
"default": "deny",
"tools": {
"update_mysql_instance": {
"limits": [
{
"counter": "update_mysql_instance_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_mysql_instance 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.
Update an existing MySQL database instance. It is categorised as a Write tool in the Linode MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for update_mysql_instance: 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 Linode MCP Server. Nothing to install.
update_mysql_instance 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 update_mysql_instance 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 update_mysql_instance. 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.
update_mysql_instance is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Linode 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.
416 Linode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.