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 t...
This record as markdown: /tools/com-googleapis-sqladmin-mcp/create-instance.md
What create_instance does on Mcp
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Required. Name of the Cloud SQL instance. This does not include the project ID. |
tags | object | — | 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 | — | 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 | — | 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 | — | 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 | — | Optional. Whether the instance is a free trial instance. If true, the instance will be created with a free trial configuration. |
ipv4Enabled | boolean | — | 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 | — | Optional. Use this to connect to the Cloud SQL instance using Private Service Access. |
pscMcpConfig | object | — | Optional. Configuration for Private Service Connect (PSC) instance creation. |
dataDiskSizeGb | string | — | Optional. Data disk size in GB. Default value is 100. |
databaseVersion | string | — | 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.
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 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 signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs create_instance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_instance, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every create_instance call is checked against it from then on.
Questions about 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"}] }. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_instance accepts 12 parameters: name, tags, tier, region, edition, project, freeTrial, ipv4Enabled, psaMcpConfig, pscMcpConfig, dataDiskSizeGb, databaseVersion. Required: name, project. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for create_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 Mcp. Nothing to install.
create_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 create_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 create_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.
create_instance is provided by the MCP server (https://sqladmin.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue