From ece48dcf20a7987491bf2cf6c7fb86a16641bb18 Mon Sep 17 00:00:00 2001 From: Josh Lambert Date: Wed, 15 Apr 2026 18:22:16 -0400 Subject: [PATCH] fix(kilo-docs): document MCP permission rules --- .../kilo-docs/pages/automate/mcp/using-in-kilo-code.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/packages/kilo-docs/pages/automate/mcp/using-in-kilo-code.md b/packages/kilo-docs/pages/automate/mcp/using-in-kilo-code.md index 8624c23a4e0..ca4443fbb8c 100644 --- a/packages/kilo-docs/pages/automate/mcp/using-in-kilo-code.md +++ b/packages/kilo-docs/pages/automate/mcp/using-in-kilo-code.md @@ -448,7 +448,7 @@ MCP tool calls use the same permission system as built-in tools. Each MCP tool's {% /tab %} {% tab label="CLI" %} -Add `alwaysAllow` entries to your server config to auto-approve specific tools: +Add `permission` entries to your config to auto-approve specific tools. MCP tool keys use the server name, an underscore, then the tool name: ```json { @@ -456,9 +456,12 @@ Add `alwaysAllow` entries to your server config to auto-approve specific tools: "my-server": { "type": "local", "command": ["npx", "-y", "my-mcp-server"], - "enabled": true, - "alwaysAllow": ["tool1", "tool2"] + "enabled": true } + }, + "permission": { + "my-server_tool1": "allow", + "my-server_tool2": "allow" } } ```