You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,6 +150,7 @@ The MongoDB MCP Server can be configured using multiple methods, with the follow
150
150
|`connectionString`| MongoDB connection string for direct database connections (optional users may choose to inform it on every tool call) |
151
151
|`logPath`| Folder to store logs |
152
152
|`disabledTools`| An array of tool names, operation types, and/or categories of tools that will be disabled. |
153
+
|`readOnly`| When set to true, only allows read and metadata operation types, disabling create/update/delete operations |
153
154
154
155
#### `logPath`
155
156
@@ -181,6 +182,19 @@ Operation types:
181
182
-`read` - Tools that read resources, such as find, aggregate, list clusters, etc.
182
183
-`metadata` - Tools that read metadata, such as list databases, list collections, collection schema, etc.
183
184
185
+
#### Read-Only Mode
186
+
187
+
The `readOnly` configuration option allows you to restrict the MCP server to only use tools with "read" and "metadata" operation types. When enabled, all tools that have "create", "update" or "delete" operation types will not be registered with the server.
188
+
189
+
This is useful for scenarios where you want to provide access to MongoDB data for analysis without allowing any modifications to the data or infrastructure.
0 commit comments