Database governance built for humans and agents — controlling changes and access across every major database.
Go cicddata-governancedata-maskingdata-securitydatabase-accessdatabase-governancedevopsdevsecopsflywaygitopsliquibasemongodbmysqloraclepostgresqlschema-migrationssecuritysql-clientsqlservertidb
fix(mcp): state the write confirmation on the MCP Access page (#21725)
Vincent Huang21ba9ad453f2
diff --git a/docs/design/mcp-capability-ladder.md b/docs/design/mcp-capability-ladder.mdindex fa76d9d5d2..a9cdbe2369 100644--- a/docs/design/mcp-capability-ladder.md+++ b/docs/design/mcp-capability-ladder.md@@ -76,7 +76,7 @@ the product.| write | Grant or revoke masking exemptions | Exempt one member from masking for a database, a schema, a table or a column, or for every database in a project, with an optional expiry · Each exemption and each removal is confirmed in the user's MCP client before it is made · Exempted data shows unmasked in query and export results | 1 WRITE method: `OrgPolicyService/UpdatePolicy`, served only through the `grant_masking_exemption` and `revoke_masking_exemption` tools, which ask the user to confirm, then add one exemption entry or remove one member from the entries whose condition matches exactly; other policy types and `CreatePolicy` and `DeletePolicy` stay refused || write | Approve or reject issues | Each decision is confirmed in the user's MCP client before it is made · Role requests are decided in the console · The approval rules and the project's self-approval setting apply, as in the console | 2 WRITE methods: `ApproveIssue`, `RejectIssue`, served only through the `decide_issue` tool, which asks the user to confirm each decision and refuses role requests || write | Run rollouts and tasks | Create a rollout · Run, skip or cancel its tasks, under the project's approval policy | 4 WRITE methods: `CreateRollout`, `BatchRunTasks`, `BatchSkipTasks`, `BatchCancelTaskRuns` |-| write | Run DML and DDL statements | INSERT, UPDATE, DELETE, CREATE, ALTER, DROP through queries, as far as the engine and the user's own permissions allow | Not a method: the statement clamp in `mcp_sql_clamp.go`, which Read-write lifts. A statement Bytebase cannot show is a read runs only through the `query_database` tool, which asks the user to confirm it when the client can show the form (`mcp_sql_write.go`) |+| write | Run DML and DDL statements | INSERT, UPDATE, DELETE, CREATE, ALTER, DROP through queries, as far as the engine and the user's own permissions allow · Where the user's MCP client supports confirmations, a query that is not a read as far as the engine can check it runs only after the user confirms it · In other clients such a query can run without asking | Not a method: the statement clamp in `mcp_sql_clamp.go`, which Read-write lifts. A statement Bytebase cannot show is a read runs only through the `query_database` tool, which asks the user to confirm it when the client can show the form (`mcp_sql_write.go`) || write | Export query results | Download results as a file. Data leaves Bytebase | 1 WRITE method: `SQLService/Export`, which requires the user's own `bb.sql.export` on the data it reads, from a role or a matching export grant, and runs only statements Bytebase can show are reads || write | Manage database housekeeping | Sync instances and databases · Saved queries | 9 WRITE methods: sync, saved-query writes || — | *Read-write stops here* | | 111 methods |@@ -222,6 +222,12 @@ the client. Activating a grant directly stays FORBIDDEN to the session. The apprrequester where the project allows self-approval; the rows promise an approval, not a secondperson.+The DML and DDL row states its confirmation with a condition, because it works unlike the confirmed+tools: `query_database` asks before a query that may write only in a client that can show the form,+and runs it at once in one that cannot, where `decide_issue` and the other confirmed tools refuse.+The confirmation covers queries only. A statement filed as an issue runs as a rollout task, under+the project's approval policy, as the rollouts row says.+The members row shows who holds which role, the groups and their members, each role's permissionsand every policy type, so an agent can tell which people an approval step waits on. Two choices inits wording are deliberate. It says *members*, not users: `UserService` reads stay EXCLUDED, so adiff --git a/frontend/src/locales/en-US.json b/frontend/src/locales/en-US.jsonindex caa6af2740..e1453cdc09 100644--- a/frontend/src/locales/en-US.json+++ b/frontend/src/locales/en-US.json@@ -3106,7 +3106,7 @@"title": "Run rollouts and tasks"},"run-statements": {- "details": "INSERT, UPDATE, DELETE, CREATE, ALTER, DROP through queries, as far as the engine and the user's own permissions allow",+ "details": "INSERT, UPDATE, DELETE, CREATE, ALTER, DROP through queries, as far as the engine and the user's own permissions allow · Where the user's MCP client supports confirmations, a query that is not a read as far as the engine can check it runs only after the user confirms it · In other clients such a query can run without asking","title": "Run DML and DDL statements"}},diff --git a/frontend/src/locales/es-ES.json b/frontend/src/locales/es-ES.jsonindex 52fe6ddeb0..b210d37326 100644--- a/frontend/src/locales/es-ES.json+++ b/frontend/src/locales/es-ES.json@@ -3106,7 +3106,7 @@"title": "Ejecutar despliegues y tareas"},"run-statements": {- "details": "INSERT, UPDATE, DELETE, CREATE, ALTER, DROP a través de consultas, hasta donde el motor y los permisos del propio usuario lo permitan",+ "details": "INSERT, UPDATE, DELETE, CREATE, ALTER, DROP a través de consultas, hasta donde el motor y los permisos del propio usuario lo permitan · Si el cliente MCP del usuario admite confirmaciones, una consulta que no es una lectura hasta donde el motor pueda comprobarlo solo se ejecuta después de que el usuario la confirme · En otros clientes, una consulta así puede ejecutarse sin preguntar","title": "Ejecutar sentencias DML y DDL"}},diff --git a/frontend/src/locales/ja-JP.json b/frontend/src/locales/ja-JP.jsonindex 38cbcb10c1..7edda1c385 100644--- a/frontend/src/locales/ja-JP.json+++ b/frontend/src/locales/ja-JP.json@@ -3106,7 +3106,7 @@"title": "ロールアウトとタスクを実行する"},"run-statements": {- "details": "クエリを通じた INSERT・UPDATE・DELETE・CREATE・ALTER・DROP。エンジンとそのユーザー自身の権限が許す範囲で行われます",+ "details": "クエリを通じた INSERT・UPDATE・DELETE・CREATE・ALTER・DROP。エンジンとそのユーザー自身の権限が許す範囲で行われます · ユーザーの MCP クライアントが確認に対応している場合、エンジンが確認できる範囲で読み取りではないクエリは、ユーザーが確認した後にのみ実行されます · それ以外のクライアントでは、そのようなクエリは確認を求めずに実行されることがあります","title": "DML と DDL のステートメントを実行する"}},diff --git a/frontend/src/locales/vi-VN.json b/frontend/src/locales/vi-VN.jsonindex 4c89417bd9..1e973c7e4a 100644--- a/frontend/src/locales/vi-VN.json+++ b/frontend/src/locales/vi-VN.json@@ -3106,7 +3106,7 @@"title": "Chạy triển khai và tác vụ"},"run-statements": {- "details": "INSERT, UPDATE, DELETE, CREATE, ALTER, DROP qua truy vấn, trong phạm vi engine và quyền của chính người dùng cho phép",+ "details": "INSERT, UPDATE, DELETE, CREATE, ALTER, DROP qua truy vấn, trong phạm vi engine và quyền của chính người dùng cho phép · Nếu ứng dụng MCP của người dùng hỗ trợ xác nhận, truy vấn không phải lệnh đọc trong phạm vi engine kiểm tra được chỉ chạy sau khi người dùng xác nhận · Ở các ứng dụng khác, truy vấn như vậy có thể chạy mà không cần hỏi","title": "Chạy câu lệnh DML và DDL"}},diff --git a/frontend/src/locales/zh-CN.json b/frontend/src/locales/zh-CN.jsonindex 93cb6ac329..6d75eab4a7 100644--- a/frontend/src/locales/zh-CN.json+++ b/frontend/src/locales/zh-CN.json@@ -3106,7 +3106,7 @@"title": "执行部署和任务"},"run-statements": {- "details": "通过查询执行 INSERT、UPDATE、DELETE、CREATE、ALTER、DROP,以引擎和该用户自身权限允许的范围为限",+ "details": "通过查询执行 INSERT、UPDATE、DELETE、CREATE、ALTER、DROP,以引擎和该用户自身权限允许的范围为限 · 如果用户的 MCP 客户端支持确认,在引擎能检查的范围内不属于读取的查询,只有在用户确认后才会执行 · 在其他客户端中,此类查询可能不经询问就执行","title": "执行 DML 和 DDL 语句"}},