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: note approval list exemptions and the tags filter gotcha
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Mukund committed
Oct 15, 2026 at 14:50 UTC
9ad080b95b4cadeffe6e9dcae23b5b8572415838
1 file changed
+6
docs/content/docs/approval-mode.mdx
+6
@@ -105,6 +105,12 @@ The session-wide `tags.require_approval` list applies to every toolkit that does
105
106
Here, Gmail only asks before `GMAIL_SEND_EMAIL`, and its destructive tools run without asking. Every other toolkit asks before its destructive tools. To keep asking before Gmail's destructive tools too, add `"tags": { "require_approval": ["destructiveHint"] }` to the `gmail` entry.
107
108
+A few more things follow from this:
109
+
110
+- A toolkit in `toolkits.require_approval` always asks, whatever else is set.
111
+- To exempt a toolkit from the session-wide tag list, give it an empty list of its own, such as `"tools": { "github": { "require_approval": [] } }`.
112
+- Setting `tools.<toolkit>.tags`, even just for `require_approval`, also replaces the session-wide tag `enable` and `disable` filter for that toolkit. To change a toolkit's approvals without touching its filter, use `tools.<toolkit>.require_approval`.
113
+
114
`require_approval` doesn't hide any tools from the agent. It can still find and call them, and the call waits for the user's approval.
115
116
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.