Read Only Mode For Production Deployments

via “read-only mode enforcement with selective tool disabling”

Create and manage Asana tasks, projects, and workspaces via MCP.

Unique: Implements access control at tool registration layer rather than runtime, preventing write tools from appearing in MCP client UI entirely when read-only mode is enabled, rather than accepting requests and rejecting them

vs others: More secure than runtime permission checks because tools are completely unavailable to clients, eliminating risk of permission bypass bugs or accidental mutations

via “read-only guest mode for code review and observation”

Real-time collaborative editing for pair programming.

Unique: Implements read-only mode by disabling edit controls in the guest's VS Code editor and filtering out edit commands at the protocol level, preventing accidental or malicious modifications while maintaining full visibility into the codebase.

vs others: More secure than screen-sharing because guests cannot accidentally or intentionally modify files; more flexible than static code review tools because guests can navigate and explore code interactively.

via “read-only-mode-for-production-deployments”

An official Qdrant Model Context Protocol (MCP) server implementation

Unique: Implements read-only mode by conditionally registering MCP tools at startup, completely removing write capabilities rather than adding runtime checks. This is a deployment-level safety mechanism rather than a per-operation guard.

vs others: Simpler and more reliable than runtime permission checks because it prevents write tools from being registered at all; more appropriate for production than relying on client-side enforcement.

via “read-only mode enforcement with configurable write operation restrictions”

** - Access and interact with Harness platform data, including pipelines, repositories, logs, and artifact registries.

Unique: Implements read-only mode as a startup configuration flag that conditionally registers write-capable toolsets, providing a simple but effective mechanism to prevent write operations in restricted environments. The implementation enforces read-only restrictions at the toolset registration level rather than per-operation, reducing complexity.

vs others: Provides simple read-only mode enforcement through startup flags, whereas fine-grained access control systems require complex permission management and per-operation authorization checks.

via “read-only deployment mode for restricted access”

** - Search dashboards, investigate incidents and query datasources in your Grafana instance

Unique: Implements read-only deployment mode that disables all write operations at the tool execution layer, enforced across all transport modes and authentication contexts. Enables restricted access deployments without requiring separate server instances or custom authorization logic.

vs others: Server-level read-only enforcement vs relying on API key permissions — provides defense-in-depth by preventing write operations even if API key has write permissions, simplifies access control for restricted deployments, and enables safe sharing of mcp-grafana with external parties.