@@ -140,11 +140,19 @@ Per-agent override: `agents.list[].tools.profile`.
140140141141| Profile | What it includes |
142142| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
143-| `full` | No restriction (same as unset) |
143+| `full` | Unrestricted baseline for broader command/control access; same as leaving `tools.profile` unset |
144144| `coding` | `group:fs`, `group:runtime`, `group:web`, `group:sessions`, `group:memory`, `cron`, `image`, `image_generate`, `music_generate`, `video_generate` |
145145| `messaging` | `group:messaging`, `sessions_list`, `sessions_history`, `sessions_send`, `session_status` |
146146| `minimal` | `session_status` only |
147147148+<Note>
149+`tools.profile: "messaging"` is intentionally narrow for channel-focused
150+agents. It leaves out broader command/control tools such as filesystem, runtime,
151+browser, canvas, nodes, cron, and gateway control. Use `tools.profile: "full"`
152+as the unrestricted baseline for broader command/control access, then trim
153+access with `tools.allow` / `tools.deny` when needed.
154+</Note>
155+148156`coding` includes lightweight web tools (`web_search`, `web_fetch`, `x_search`)
149157but not the full browser-control tool. Browser automation can drive real
150158sessions and logged-in profiles, so add it explicitly with
@@ -156,6 +164,16 @@ under the plugin key `bundle-mcp`. Add `tools.deny: ["bundle-mcp"]` when you
156164want a profile to keep its normal built-ins but hide all configured MCP tools.
157165The `minimal` profile does not include bundle MCP tools.
158166167+Example (broadest tool surface by default):
168+169+```json5
170+{
171+ tools: {
172+ profile: "full",
173+ },
174+}
175+```
176+159177### Tool groups
160178161179Use `group:*` shorthands in allow/deny lists:
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。