MCP servers 2026-05-22 09:39 UTC
mcp-bigquery-server
Committed by ergut. Update Category: Documentation Updates. Commit details: docs: extract PROTECTION.md, surface read-only design, fix config-file claim. This update refines the documentation for easier onboarding.
CommitRaw commit message
docs: extract PROTECTION.md, surface read-only design, fix config-file claim - Move ~190 lines of security/protection configuration into PROTECTION.md so the README focuses on getting up and running. README drops from 467 to 277 lines; PROTECTION.md is the new home for the threat model, protection modes, field-level restrictions, sensitive field scanner, and required IAM permissions. - Surface read-only design as a primary feature: mention it in the intro paragraph and make it the first bullet of "What Can It Do?", explaining that BigQuery's own dry-run planner rejects INSERT/UPDATE/DELETE/DROP/ TRUNCATE/EXPORT DATA/MERGE. Remove the misleading "read-only is a limitation" framing from Current Limitations. - Fix inaccurate --config-file default: the code (src/index.ts) treats an omitted --config-file flag as Simple Mode with no protection; there is no implicit ./config.json fallback. - Fix --maximum-bytes-billed omission in the "configurable safe limits" bullet. - Generalize Claude Desktop references throughout to "MCP client" with Claude Desktop and Claude Code shown as examples. - Deduplicate the Local Build section into one JSON block plus a single Protected Mode note. - Promote Configuration from a Quick Start subsection to a top-level section, since CLI args and config.json apply to all modes. - In PROTECTION.md, clarify that the "cooperative guardrails" caveat applies to field/table restrictions only; read-only enforcement is BigQuery-AST-authoritative.