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 ...
Risk signalsAccepts raw HTML/template content (body)
Part of the Mcp server.
Free to start. No card required.
AI agents invoke postgres_upgrade_precheck to trigger processes or run actions in Mcp. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
postgres_upgrade_precheck can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"postgres_upgrade_precheck": {
"limits": [
{
"counter": "postgres_upgrade_precheck_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Mcp policy for all 15 tools.
These attack patterns abuse exactly the kind of access postgres_upgrade_precheck gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
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.
Deterministic rules across all 15 Mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.