relational-database-mcp-cloudbase

To provision CloudBase MySQL, use manageSqlDatabase to handle the instance lifecycle and poll its async status. Once readiness is verified, initialize required tables, indexes, and security rules to complete the schema setup.

Safe SQL execution separates read and write operations by using querySqlDatabase for controlled read-only SELECT checks, while manageSqlDatabase handles mutating DDL and DML operations to prevent unsafe writes.

Yes, you can update table access permissions for CloudBase MySQL via MCP. Use readSecurityRule to audit current per-table permissions, then apply writeSecurityRule to harden access and align it with your use case.

The best way to run read-only checks before mutating a CloudBase MySQL schema is to execute controlled SELECT queries via querySqlDatabase. This verifies current provisioning state and data before applying DDL or DML changes.

Yes, MCP tools are required to manage CloudBase MySQL safely. They enforce required lifecycle checks for provisioning and ensure security rule updates and SQL mutations are executed without risking unsafe write operations.