docs(tools): note explicit alsoAllow needed under restrictive profile… · openclaw/openclaw@ad7fa6c
vincentkoc
·
2026-04-30
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -159,6 +159,10 @@ sessions and logged-in profiles, so add it explicitly with
|
159 | 159 | `tools.alsoAllow: ["browser"]` or a per-agent |
160 | 160 | `agents.list[].tools.alsoAllow: ["browser"]`. |
161 | 161 | |
| 162 | +<Note> |
| 163 | +Configuring `tools.exec` or `tools.fs` under a restrictive profile (`messaging`, `minimal`) does not implicitly widen the profile's allowlist. Add explicit `tools.alsoAllow` entries (for example `["exec", "process"]` for exec, or `["read", "write", "edit"]` for fs) when you want a restrictive profile to use those configured sections. OpenClaw logs a startup warning when a config section is present without a matching `alsoAllow` grant. |
| 164 | +</Note> |
| 165 | + |
162 | 166 | The `coding` and `messaging` profiles also allow configured bundle MCP tools |
163 | 167 | under the plugin key `bundle-mcp`. Add `tools.deny: ["bundle-mcp"]` when you |
164 | 168 | want a profile to keep its normal built-ins but hide all configured MCP tools. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
