update_instance
Partially updates the configuration settings of a Cloud SQL instance. * This tool returns a long-running operation. Use the get_operation tool to poll its status until the operation completes. * Some update operations, such as changing the edition upgrade or instance tier, etc might cause the ins...
This record as markdown: /tools/com-googleapis-sqladmin-mcp/update-instance.md
What update_instance does on Mcp
AI agents use update_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 |
|---|---|---|---|
tier | string | — | Optional. The tier (or machine type) for this instance. format: db-custom-{CPUs}-{Memory}. |
edition | string | — | Optional. The edition of the instance, can be ENTERPRISE or ENTERPRISE_PLUS. |
project | string | Yes | Required. Project ID of the project that contains the instance. |
instance | string | Yes | Required. Cloud SQL instance ID. This does not include the project ID. |
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. Configuration for Private Service Access (PSA) instance update. |
pscMcpConfig | object | — | Optional. Configuration for Private Service Connect (PSC) instance update. |
dataApiAccess | string | — | Optional. The settings for controlling data API access to an instance. |
databaseFlags | array | — | Optional. The database flags. |
dataDiskSizeGb | string | — | Optional. Data disk size in GB. |
dataCacheConfig | object | — | Optional. Configuration for the data cache. A data cache can improve performance for read-heavy workloads by caching frequently accessed data in-memory. |
googleMlIntegrationEnabled | boolean | — | Optional. Enables Cloud SQL instances to connect to Vertex AI to pass requests for real-time predictions and insights to the AI. The default value is false. Thi |
Parameters from the server's own tool schema.
Why update_instance is rated Medium
This tool modifies Cloud SQL instance configuration settings, which is a Write operation (creates or modifies data reversibly). It is not Destructive because updates are reversible and no data is permanently deleted. It is not Execute because it doesn't run arbitrary code or queries—it applies predefined configuration changes.
From the tool's definition Tool description states it 'Partially updates the configuration settings of a Cloud SQL instance.' The word 'updates' indicates modification of existing data/configuration.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs update_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 update_instance, this is the rule to start with:
update_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 update_instance call is checked against it from then on.
Questions about update_instance
Partially updates the configuration settings of a Cloud SQL instance. * This tool returns a long-running operation. Use the get_operation tool to poll its status until the operation completes. * Some update operations, such as changing the edition upgrade or instance tier, etc might cause the instance to restart, resulting in downtime. Before you proceed with such operations, get confirmation from the user. 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.
update_instance accepts 12 parameters: tier, edition, project, instance, ipv4Enabled, psaMcpConfig, pscMcpConfig, dataApiAccess, databaseFlags, dataDiskSizeGb, dataCacheConfig, googleMlIntegrationEnabled. Required: project, instance. 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 update_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.
update_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_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_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_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