Kiro Data Debug

Data Debug (Kiro / Kiro Crew)

This is the Kiro-native port of the Codex data-debug skill. The engine — the db-debug:latest Docker image (built from the bundled Dockerfile), its client set, the read-only-by-default workflow, and the transport/mutation safety contracts — is agent-agnostic and carries over unchanged. Only the invocation and shell contract are Kiro-specific:

• Invoke this skill with the $kiro-data-debug inline token in chat.
• Run every docker … command with Kiro's shell tool.
• The read-only default, the mutation boundary, and the secret-handling rules below are hard gates and align with this agent's own safety guardrails: never place connection URIs, passwords, or tokens in a shell command argument or in chat — pass them through a user-provided --env-file; and treat approval for one exact statement as approval for that statement only.

Use only the db-debug:latest image for supported database work. Treat the database, its credentials, and returned data as sensitive.

Workflow

1. Confirm the target engine, environment, database, and diagnostic question. Resolve ambiguity before connecting to production or another sensitive environment.

2. Verify Docker and the required local image before using any database client:

   docker version
   docker image inspect db-debug:latest
   

   If either command fails, stop and report the blocker. Do not pull, build, retag, or substitute an image unless the user explicitly asks for that exact action.

3. If client availability is uncertain, run:

   docker run --rm db-debug:latest bash -lc 'sql -version && sqlplus -v && psql --version && mysql --version && mongosh --version && mongo-legacy --version && redis-cli --version && sqlcmd -? >/dev/null && bcp -v && mssql-connect --version && if command -v sqlcmd17 >/dev/null; then sqlcmd17 -? >/dev/null && bcp17 -v; fi'
   

4. Classify the requested operation before execution:

   • Read-only: connectivity checks, metadata inspection, bounded reads, and non-mutating query plans.
   • Sensitive export: dumps, bulk reads, or queries likely to expose personal, credential, financial, or production data. Require an explicit user request and minimize the output.
   • Mutation: writes, deletes, DDL, flushes, procedure calls with side effects, configuration, permissions, maintenance, or administration. Follow the mutation boundary below.

5. Use the least-privileged, read-only database account available. Client-side intent is not a security boundary; a query that starts with SELECT can still call a mutating function.

6. Run the narrowest useful command, limit returned rows or keys, and summarize results without reproducing secrets or unnecessary sensitive values.

Safety Rules

• Keep all operations read-only unless the user explicitly approves the exact mutation in the current conversation.
• Before an approved mutation, show the exact target, statement or command, expected effect, and rollback or recovery path. Do not interpret approval for one statement as approval for a batch, retry, broader target, or follow-up operation.
• Do not run stored procedures, user-defined functions, triggers, EXPLAIN ANALYZE on mutating statements, or commands with unclear side effects as read-only work.
• Never place connection URIs, passwords, tokens, certificates, or other secrets in chat, source files, shell command arguments, or captured logs. Pass connection settings through a user-provided environment file with docker run --env-file.
• Keep environment files outside the repository, restrict their permissions, never print them, and delete temporary credential files after use when their lifecycle is owned by the task.
• TLS is optional. Prefer a verified TLS connection when the endpoint supports it, but allow plaintext transport, unverified certificates, or disabled hostname verification when required by the target or requested by the user. Use the narrowest relaxation that works, do not disable authentication as part of this allowance, and report the resulting transport security mode.
• Always use --rm. Do not mount the Docker socket, mount database data directories, use --privileged, or add capabilities. Avoid host filesystem mounts unless a user-requested import or export requires a specific path.
• Prefer explicit timeouts supported by the selected client or server. Avoid unbounded scans, full collection reads, keyspace-wide Redis commands, and production query-plan execution that could create material load.
• Do not switch MongoDB clients to work around authentication, DNS, or networking failures. Configure the selected client explicitly when plaintext transport or relaxed TLS verification is required.
• Report the database identity and scope before substantive diagnostics when a wrong-target connection would be risky.

Connection Pattern

Use:

docker run --rm --env-file <env-file> db-debug:latest bash -lc '<read-only command>'

Network routing:

• For a database on the macOS or Windows Docker host, use host.docker.internal.
• For a database on the Linux Docker host, add --add-host=host.docker.internal:host-gateway.
• For a database in another container, attach this container to the same explicit Docker network.

Do not expand secret-bearing environment variables in the host shell. Expand them only inside the container's quoted bash -lc command.

Transport Security

Verified TLS is preferred but not required. Connections may use one of these modes:

• Verified TLS: encrypt traffic and verify both the certificate chain and hostname.
• Relaxed TLS: keep encryption while trusting an unverified certificate, skipping hostname verification, or both.
• Plaintext: disable TLS when the server does not support it or the diagnostic context requires it.

Do not silently downgrade a connection. State the selected mode, configure it explicitly through the client or the user-provided environment file, and preserve authentication. Common client controls include:

• PostgreSQL: set PGSSLMODE=disable for plaintext or PGSSLMODE=require for encrypted transport without certificate or hostname verification.
• MySQL: use --ssl-mode=DISABLED for plaintext or --ssl-mode=REQUIRED for encrypted transport without CA or hostname verification.
• MongoDB: set tls=false for plaintext, or set tls=true, tlsAllowInvalidCertificates=true, and/or tlsAllowInvalidHostnames=true in the URI as narrowly as needed.
• Redis: omit --tls for plaintext; use --tls --insecure for encrypted transport without certificate verification.
• Microsoft SQL Server: use -No to make encryption optional or -Nm to require it with the default ODBC Driver 18 sqlcmd; add -C when encrypted transport must trust an unverified server certificate. The ODBC Driver 17 sqlcmd17 compatibility client makes encryption optional by default; use -N -C when encrypted transport with an unverified certificate is required. For mssql-connect, MSSQL_ENCRYPT defaults to false; set it to true and set MSSQL_TRUST_SERVER_CERTIFICATE=true only when an encrypted connection must accept an unverified certificate. Replace MSSQL with the selected environment-variable prefix.
• Oracle: select a non-TLS connect descriptor for plaintext. For TCPS, relax certificate or distinguished-name matching only in task-owned client configuration and do not overwrite an existing Oracle network configuration.

Treat these transport relaxations separately from authentication. Do not disable or bypass authentication unless the user explicitly requests that distinct action and the target is intentionally configured for it.

Client Selection

• PostgreSQL: psql
• MySQL: mysql
• Modern MongoDB: mongo-connect
• MongoDB 3.4: mongo-connect --server-version 3.4
• Redis: redis-cli
• Microsoft SQL Server: use the ODBC Driver 18 sqlcmd with an explicit transport mode. After a confirmed ODBC TLS/pre-login compatibility failure, use the Microsoft JDBC mssql-connect client and report the fallback. It reads SQL from standard input, requires an environment-variable prefix, requests applicationIntent=ReadOnly, does not require encryption unless <PREFIX>_ENCRYPT=true, limits results to 100 rows, and applies 10-second login, socket, and query timeouts. On AMD64, sqlcmd17 remains available for legacy ODBC compatibility. Driver 17 is unavailable in the ARM64 image. Use bcp or bcp17 only for an explicitly requested bulk transfer.
• Oracle: prefer sqlplus; use sql only when SQLcl features are required

Always use mongo-connect, not mongosh or mongo-legacy directly.

Read-Only Examples

PostgreSQL:

docker run --rm --env-file db.env db-debug:latest bash -lc 'psql --set --command "BEGIN READ ONLY; SELECT current_database(), current_user; COMMIT;"'

MySQL:

docker run --rm --env-file db.env db-debug:latest bash -lc 'mysql --host="$MYSQL_HOST" --port="${MYSQL_PORT:-3306}" --user="$MYSQL_USER" "$MYSQL_DATABASE" --execute "START TRANSACTION READ ONLY; SELECT DATABASE(), CURRENT_USER(); COMMIT;"'

Modern MongoDB:

docker run --rm --env-file db.env db-debug:latest bash -lc 'mongo-connect "$MONGODB_URI" --quiet --eval "db.runCommand({ ping: 1 })"'

MongoDB 3.4:

docker run --rm --env-file db.env db-debug:latest bash -lc 'mongo-connect --server-version 3.4 "$MONGODB_URI" --quiet --eval "db.runCommand({ ping: 1 })"'

Redis:

docker run --rm --env-file db.env db-debug:latest bash -lc 'redis-cli -h "$REDIS_HOST" -p "${REDIS_PORT:-6379}" PING'

Microsoft SQL Server:

docker run --rm --env-file db.env db-debug:latest bash -lc 'sqlcmd -No -S "$MSSQL_HOST,$MSSQL_PORT" -U "$MSSQL_USER" -d "$MSSQL_DATABASE" -K ReadOnly -Q "SELECT DB_NAME(), SUSER_SNAME();"'

Microsoft SQL Server compatibility fallback on AMD64 after a confirmed Driver 18 TLS/pre-login failure:

docker run --rm --env-file db.env db-debug:latest bash -lc 'sqlcmd17 -S "$MSSQL_HOST,$MSSQL_PORT" -U "$MSSQL_USER" -d "$MSSQL_DATABASE" -K ReadOnly -Q "SELECT DB_NAME(), SUSER_SNAME();"'

Microsoft SQL Server JDBC fallback after a confirmed ODBC TLS/pre-login failure:

printf 'SELECT DB_NAME(), SUSER_SNAME();' | docker run --rm --interactive --env-file db.env db-debug:latest mssql-connect MSSQL

Oracle:

docker run --rm --env-file db.env db-debug:latest bash -lc 'printf "connect %s/%s@%s\nSET TRANSACTION READ ONLY;\nSELECT global_name FROM global_name;\nCOMMIT;\nexit\n" "$ORACLE_USER" "$ORACLE_PASSWORD" "$ORACLE_DSN" | sqlplus -s /nolog'

Adapt variable names to the user-provided environment file without exposing their values.

Mutation Boundary

If the user requests a mutation:

1. Use read-only queries to verify the target and estimate impact.
2. Present the exact mutation and recovery plan.
3. Wait for explicit approval for that exact operation.
4. Execute only the approved operation through db-debug:latest.
5. Verify the outcome with a separate read-only query and report it.

If exact approval, target identity, credentials, recovery expectations, or side effects remain unclear, stop and ask the user to decide. Do not use a workaround.