relational-database-mcp-cloudbase

Use the four supported MCP tools for CloudBase: executeReadOnlySQL for SELECT queries, executeWriteSQL for INSERT/UPDATE/DELETE/DDL, readSecurityRule to inspect access rules, and writeSecurityRule to modify them. Always verify reads before writes and provide explicit summaries before destructive operations to enforce safety constraints.

Standard SDKs bypass the safety-first validation patterns required for CloudBase operations. MCP tools enforce explicit intent verification and prevent data corruption by requiring read verification before writes and mandatory operation summaries on destructive actions.

Initiate a read operation with executeReadOnlySQL to validate the target data, then plan and execute your write with executeWriteSQL after confirming results. This procedural separation prevents accidental data corruption in production environments.

Yes. Use readSecurityRule to audit current access controls and writeSecurityRule to modify them. This enables security hardening and compliance auditing workflows without embedding SDKs.

CloudBase MCP supports read-only queries (SELECT), write and DDL operations (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP), and security rule inspection and modification for data migrations, inspections, and security hardening scenarios.

Yes. Safety constraints mandate that you verify data with executeReadOnlySQL before performing writes via executeWriteSQL, and you must provide explicit operation summaries before destructive actions to prevent unintended data loss.