postgres_upgrade_precheck
Checks if a Cloud SQL for PostgreSQL instance is ready for a major version upgrade to the specified target version. The target_database_version MUST be provided in the request (e.g., POSTGRES_15). This tool helps identify potential issues *before* attempting the actual upgrade, reducing the risk ...
This record as markdown: /tools/com-googleapis-sqladmin-mcp/postgres-upgrade-precheck.md
What postgres_upgrade_precheck does on Mcp
AI agents invoke postgres_upgrade_precheck to trigger actions in Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | Yes | Required. The context for request to perform the pre-check major version upgrade operation. |
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. |
location | string | — | Optional. Region of the Cloud SQL instance. |
Parameters from the server's own tool schema.
Why postgres_upgrade_precheck is rated High
postgres_upgrade_precheck triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs postgres_upgrade_precheck 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 postgres_upgrade_precheck, this is the rule to start with:
postgres_upgrade_precheck stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 postgres_upgrade_precheck call is checked against it from then on.
Questions about postgres_upgrade_precheck
Checks if a Cloud SQL for PostgreSQL instance is ready for a major version upgrade to the specified target version. The target_database_version MUST be provided in the request (e.g., POSTGRES_15). This tool helps identify potential issues *before* attempting the actual upgrade, reducing the risk of failure or downtime. This tool is only supported for PostgreSQL primary instances and does not run on read replicas. The precheck typically evaluates: - Database schema compatibility with the target version. - Cloud SQL limitations and unsupported features. - Instance resource constraints (e.g., number of relations). - Compatibility of current database settings and extensions. - Overall instance health and readiness. This tool returns a long-running operation. Use the get_operation tool with the operation name returned by this call to poll its status. IMPORTANT: Once the operation status is DONE, the detailed precheck results are available within the Operation resource. You will need to inspect the response from get_operation. The findings are located in the pre_check_major_version_upgrade_context.pre_check_response field. The findings are structured, indicating: - INFO: General information. - WARNING: Potential issues that don't block the upgrade but should be reviewed. - ERROR: Critical issues that MUST be resolved before attempting the upgrade. Each finding should include a message and any required actions. Addressing any reported issues is crucial before proceeding with the major version upgrade. If pre_check_response is empty or missing, it indicates that no issues were identified during the precheck. Running this precheck does not impact the instance's availability. It is categorised as a Execute tool in the Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
postgres_upgrade_precheck accepts 4 parameters: body, project, instance, location. Required: body, 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 postgres_upgrade_precheck: 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.
postgres_upgrade_precheck is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the postgres_upgrade_precheck 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 postgres_upgrade_precheck. 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.
postgres_upgrade_precheck 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