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: docs/features/mcp.md
+41Lines changed: 41 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -156,6 +156,47 @@ await using var session = await client.CreateSessionAsync(new SessionConfig
156
156
});
157
157
```
158
158
159
+
## Tool Configuration
160
+
161
+
You can control which tools are available to an MCP server using the `tools` field.
162
+
163
+
### Allow all tools
164
+
165
+
Use `"*"` to enable all tools provided by the MCP server:
166
+
167
+
```typescript
168
+
tools: ["*"]
169
+
```
170
+
171
+
---
172
+
173
+
### Allow specific tools
174
+
175
+
Provide a list of tool names to restrict access:
176
+
177
+
```typescript
178
+
tools: ["bash", "edit"]
179
+
```
180
+
181
+
Only the listed tools will be available to the agent.
182
+
183
+
---
184
+
185
+
### Disable all tools
186
+
187
+
Use an empty array to disable all tools:
188
+
189
+
```typescript
190
+
tools: []
191
+
```
192
+
193
+
---
194
+
195
+
### Notes
196
+
197
+
- The `tools` field defines which tools are allowed.
198
+
- There is no separate `allow` or `disallow` configuration — tool access is controlled directly through this list.
199
+
159
200
## Quick Start: Filesystem MCP Server
160
201
161
202
Here's a complete working example using the official [`@modelcontextprotocol/server-filesystem`](https://www.npmjs.com/package/@modelcontextprotocol/server-filesystem) MCP server:
0 commit comments