Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs: drop the numbered steps from requiring approval
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Mukund committed
Oct 15, 2026 at 15:31 UTC
c45441c848e44a8e6739ef9439e528be44a984dc
1 file changed
+8
-24
docs/content/docs/approval-mode.mdx
+8
-24
@@ -16,15 +16,7 @@ Approval mode is experimental, and its SDK options may change. Answering questio
16
17
You choose which tools ask first when you create or update a session.
18
19
-### 1. Enable toolkits
20
-
21
-List the toolkits the agent can use in `toolkits.enable`:
22
-
23
-```python
24
-toolkits={"enable": ["gmail", "github"]}
25
-```
26
-
27
-### 2. Allow, ask first or block tools by type
19
+### By type of tool
20
21
Every tool has a [tag](/docs/tool-tags) for the type of action it takes:
22
@@ -35,13 +27,7 @@ Every tool has a [tag](/docs/tool-tags) for the type of action it takes:
27
| `updateHint` | Update |
28
| `destructiveHint` | Destructive |
29
38
-Use the tags to set what happens to each type of tool:
39
-
40
-- **Allow:** leave the tag out. These tools run without asking.
41
-- **Ask first:** add the tag to `tags.require_approval`. These tools wait for the user's approval.
42
-- **Block:** add the tag to `tags.disable`. The agent can't see or call these tools.
43
-
44
-For example, to allow tools that read, ask before tools that create or update, and block tools that delete:
30
+To make every tool of a type ask first, add its tag to `tags.require_approval`. Tools whose tags you leave out run without asking, and tools whose tags are in `tags.disable` are [blocked](/docs/configuring-sessions#filtering-tools-by-tags). For example, to ask before tools that create or update, and block tools that delete:
31
32
```python
33
tags={
@@ -50,13 +36,11 @@ tags={
36
}
37
```
38
53
-### 3. Override for specific toolkits
54
-
55
-Step 2 applies to the tools of every toolkit. To handle a toolkit's tools differently, add an override for it under `tools.<toolkit>`.
39
+### Overriding for a toolkit
40
57
-The override replaces step 2 for that toolkit. Step 2 no longer applies to its tools at all, so the override has to cover all of them. You can override by type or tool by tool.
41
+The session-wide `tags` apply to the tools of every toolkit. To handle a toolkit's tools differently, override them under `tools.<toolkit>`. The override replaces the session-wide `tags` for that toolkit, so it has to cover all of its tools. You can override by type or tool by tool.
42
59
-**By type.** Set `tools.<toolkit>.tags` the same way as step 2. Repeat anything from step 2 you still want for the toolkit. For example, this override makes GitHub's tools that delete ask first instead of being blocked. Tools that create or update are listed again so they still ask first:
43
+**By type.** Set `tools.<toolkit>.tags` the same way as the session-wide `tags`, and repeat anything from them you still want for the toolkit. For example, this override makes GitHub's tools that delete ask first instead of being blocked. Tools that create or update are listed again so they still ask first:
44
45
```python
46
tools={
@@ -77,11 +61,11 @@ tools={
61
}
62
```
63
80
-Always set `require_approval` in a tool-by-tool override, even to `[]`. Without it, the tools you list still ask first if step 2 says so.
64
+Always set `require_approval` in a tool-by-tool override, even to `[]`. Without it, the tools you list still ask first if the session-wide `tags` say so.
65
66
Use one or the other for a toolkit, not both.
67
84
-### Putting it together
68
+### Example
69
70
<Tabs groupId="language" items={['Python', 'TypeScript']} persist>
71
<Tab value="Python">
@@ -135,7 +119,7 @@ With this session:
119
120
- **GitHub** is overridden by type. Tools that read run freely, and tools that create, update or delete ask first.
121
- **Gmail** is overridden tool by tool. Fetching emails runs freely, sending asks first, and no other Gmail tools are available.
138
-- **Any other toolkit** isn't enabled. If you enabled one without an override, step 2 would apply to its tools: tools that read run freely, tools that create or update ask first, and tools that delete are blocked.
122
+- **Any other toolkit** isn't enabled. If you enabled one without an override, the session-wide `tags` would apply to its tools: tools that read run freely, tools that create or update ask first, and tools that delete are blocked.
123
124
Asking first doesn't hide a tool from the agent. It can still find and call it, and the call waits for the user's approval. This also applies to each tool call inside `COMPOSIO_MULTI_EXECUTE_TOOL`, the meta tool agents use to run app tools. A batch with two calls that need approval comes back with two questions.
125