# create_instance Initiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the get_operation tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * After you use the create_instance tool to create an instance, you can use the create_user tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set ipv4_enabled to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set free_trial to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of data_api_access is set to ALLOW_DATA_API by default. This setting lets you execute SQL statements using the execute_sql tool and the executeSql API. Unless otherwise specified, a newly created instance uses the default instance configuration of a development environment. The following is the default configuration for an instance in a development environment: { "tier": "db-perf-optimized-N-2", "data_disk_size_gb": 100, "region": "us-central1", "database_version": "POSTGRES_18", "edition": "ENTERPRISE_PLUS", "availability_type": "ZONAL", "tags": [{"environment": "dev"}] } The following configuration is recommended for an instance in a production environment: { "tier": "db-perf-optimized-N-8", "data_disk_size_gb": 250, "region": "us-central1", "database_version": "POSTGRES_18", "edition": "ENTERPRISE_PLUS", "availability_type": "REGIONAL", "tags": [{"environment": "prod"}] } The following instance configuration is recommended for SQL Server: { "tier": "db-perf-optimized-N-8", "data_disk_size_gb": 250, "region": "us-central1", "database_version": "SQLSERVER_2022_STANDARD", "edition": "ENTERPRISE", "availability_type": "REGIONAL", "tags": [{"environment": "prod"}] } Agent View of the PolicyLayer registry record for `create_instance`. HTML page: https://policylayer.com/tools/com-googleapis-sqladmin-mcp/create-instance ## Facts - Tool: `create_instance` - Server: Mcp (`https://sqladmin.googleapis.com/mcp`) — https://policylayer.com/tools/com-googleapis-sqladmin-mcp.md - Homepage: https://github.com/https://sqladmin.googleapis.com/mcp - Risk category: Write (Medium risk) - Registry record: grade F, identity unverified - Server auth posture: open - Server rate-limited: no - Parameters: 12 (2 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `name` | string | yes | Required. Name of the Cloud SQL instance. This does not include the project ID. | | `tags` | object | no | Optional. Input only. Tag keys and tag values that are bound to this instance. You must represent each item in the map as: `"" : ""`. For example, a single reso | | `tier` | string | no | Optional. The tier (or machine type) for this instance. If not specified: - For `ENTERPRISE_PLUS` edition, the default tier is `db-perf-optimized-N-2`, which gi | | `region` | string | no | Optional. The geographical region of the Cloud SQL instance. For example, `us-central1`, `europe-west1`, and `asia-east1`. If not specified, the default value i | | `edition` | string | no | Optional. The edition of the instance, can be ENTERPRISE or ENTERPRISE_PLUS. If not specified: - For Postgres and Mysql, the default value is ENTERPRISE_PLUS. - | | `project` | string | yes | Required. Project ID of the project to which the newly created Cloud SQL instances should belong. | | `freeTrial` | boolean | no | Optional. Whether the instance is a free trial instance. If true, the instance will be created with a free trial configuration. | | `ipv4Enabled` | boolean | no | Optional. Whether to enable public IP for the instance. Enabling this flag makes the resource accessible from the public internet, which is a security risk if n | | `psaMcpConfig` | object | no | Optional. Use this to connect to the Cloud SQL instance using Private Service Access. | | `pscMcpConfig` | object | no | Optional. Configuration for Private Service Connect (PSC) instance creation. | | `dataDiskSizeGb` | string | no | Optional. Data disk size in GB. Default value is 100. | | `databaseVersion` | string | no | Optional. The database engine type and version. The default value is `POSTGRES_18`. For Mysql, it can be `MYSQL_8_4`, `MYSQL_8_0`, `MYSQL_5_7`, etc. For Postgre | Parameters from the server's own tool schema. ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "create_instance", "arguments": { "name": "", "project": "" } } } ``` ## Why create_instance is rated Medium Creating a Cloud SQL instance is a write operation that modifies cloud infrastructure by adding a new managed database resource. While significant in scope and blast radius (high severity due to potential cost implications and infrastructure changes), it is reversible through deletion and does not meet the threshold for Destructive (which requires irreversible data loss) or Financial (no direct money movement). From the tool's own definition: "Tool 'initiates the creation of a Cloud SQL instance' which is a reversible resource creation operation. The description explicitly states it creates an instance and returns a long-running operation for status monitoring." Risk signals: High parameter count (15 properties) ## Use case AI agents use create_instance to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp: ```json { "version": "1", "default": "deny", "tools": { "create_instance": { "limits": [ { "counter": "create_instance_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## Other tools on Mcp (14) - `execute_sql` — Execute — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/execute-sql.md - `execute_sql_readonly` — Execute — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/execute-sql-readonly.md - `postgres_upgrade_precheck` — Execute — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/postgres-upgrade-precheck.md - `get_instance` — Read — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/get-instance.md - `get_operation` — Read — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/get-operation.md - `list_instances` — Read — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/list-instances.md - `list_users` — Read — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/list-users.md - `clone_instance` — Write — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/clone-instance.md - `create_backup` — Write — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/create-backup.md - `create_user` — Write — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/create-user.md - `import_data` — Write — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/import-data.md - `restore_backup` — Write — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/restore-backup.md - `update_instance` — Write — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/update-instance.md - `update_user` — Write — https://policylayer.com/tools/com-googleapis-sqladmin-mcp/update-user.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-googleapis-sqladmin-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-googleapis-sqladmin-mcp