create_mysql_instance

What create_mysql_instance does on Linode MCP Server

AI agents use create_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.

Why create_mysql_instance is rated Medium

This tool creates a new cloud database resource, which is a reversible Write operation. It has high severity because creating database instances incurs infrastructure costs, consumes account quotas, and could impact billing or resource limits, though the action itself can be undone by deletion. It does not move money directly (Financial) nor execute arbitrary code (Execute), nor is it destructive in nature.

From the tool's definition Tool name is 'create_mysql_instance' and description states 'Create a new MySQL database instance'. The verb 'create' and action of instantiating a new database resource indicates data/resource creation.

The rule that runs create_mysql_instance safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_mysql_instance, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_mysql_instance": {
      "limits": [
        {
          "counter": "create_mysql_instance_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about create_mysql_instance