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: correct session proxy permission callout
Mukund committed
Sep 15, 2026 at 18:45 UTC
6c2bcc554ffaaa8d5d23dcc4077d9f7d677d7a33
1 file changed
+1
-1
docs/content/docs/extending-sessions/proxy-execute.mdx
+1
-1
@@ -11,7 +11,7 @@ The session is already scoped to a [userID](/docs/how-composio-works), so you pa
11
Proxy execute is a building block, not just a fallback. Use it to build experiences on top of Composio that reach past predefined tools, like the [Pi + Slack bot example](/examples/general-agent-with-pi#reach-the-gaps-with-the-proxy), which drops down to the proxy for the Slack Web API calls the toolkit doesn't wrap as tools. We'll link more examples here as we add them.
12
13
<Callout title="Use a scoped API key">
14
-Proxy execute is gated behind its own permission. Authenticate with a [scoped project API key](/reference/authenticating-to-composio/project-api-key-permissions) that has the **Proxy execute** permission granted. Default full-access keys already include it.
14
+Authenticate with a [scoped project API key](/reference/authenticating-to-composio/project-api-key-permissions) with **Session Tool Execution** enabled. Default full-access keys already include this permission.
15
</Callout>
16
17
## When to use it