@devries-cameron20 / composio Mirror · read-only / commits / 54f65c563
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 12:15 UTC

docs: session proxy execute requires the Proxy execute permission (#4554)

This PR: - replaces https://github.com/ComposioHQ/composio/pull/4474 (D5), which was merged into the D2 branch by mistake and conflicted with the rewritten permissions reference on `next`; https://github.com/ComposioHQ/composio/pull/4471 has been trimmed back to D2 only - rewrites the change against the current "Session tool execution" / "Proxy execute (Legacy)" layout instead of the pre-rewrite page the original targeted - Session tool execution: drops the `/tool_router/session/{session_id}/proxy_execute` row and says proxy execution is not included; Proxy execute (Legacy): states it is the only permission that grants the session proxy route, from `session.proxyExecute()` or from the session's sandbox - Proxy execute page callout: requires Proxy execute; Session tool execution alone does not cover it - KB article `platform-project-api-key-permissions` (source under `docs/kb/articles`, generated guide regenerated with `bun run generate:kb`): same correction - merge after: ComposioHQ/platform#12846. Until it deploys, `next` is correct and this page must not go live. Kept as a draft for that reason PRD: https://app.notion.com/p/composio/Session-Governance-via-hints-Across-toolkits-3daf261a6dfe80df8e0ce337a2b26e08 Linear workstream: https://linear.app/composio/project/sessions-execution-governance-a0942233a0d0 Verification, run in `docs/` on this branch: `bun run types:check` passes, `bun run lint:links` reports 0 errors. `pnpm exec prettier --check` flags the touched mdx files on `next` already, so no reformatting was applied.

Alberto Schiabel committed Sep 21, 2026 at 18:05 UTC 54f65c563724542157e189bde78be13d7e0c20f9
4 files changed +10 -11
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 -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.
14 +Authenticate with a [scoped project API key](/reference/authenticating-to-composio/project-api-key-permissions) that has **Proxy execute** enabled. Session tool execution alone does not cover `session.proxyExecute()` or proxy calls made from that session's sandbox. Default full-access keys already include this permission.
15 </Callout>
16
17 ## When to use it
docs/content/kb/guide/platform-project-api-key-permissions.mdx
+1 -1
@@ -32,4 +32,4 @@ Create a correctly scoped Project API key or use an appropriate full-access Proj
32
33 ## Session tool execution requires write access
34
35 -Set **Session tool execution** to Write to search and execute tools through a session or its MCP server. This permission also covers session proxy requests and allows the key to invoke any tool exposed by the session-linked MCP server.
35 +Set **Session tool execution** to Write to search and execute tools through a session or its MCP server. This permission allows the key to invoke any tool exposed by the session-linked MCP server. It does not cover session proxy requests; those need **Proxy execute**.
docs/content/reference/authenticating-to-composio/project-api-key-permissions.mdx
+7 -8
@@ -143,14 +143,13 @@ The Session config read routes below are experimental and require Session config
143
144 ## Session tool execution
145
146 -Search and execute tools through sessions and session-linked MCP servers. This includes session proxy execution, so it grants every execution capability exposed through a session.
146 +Search and execute tools through sessions and session-linked MCP servers. Session proxy execution is not included; grant [Proxy execute](#proxy-execute-legacy) for that.
147
148 -| Access | Method | Route |
149 -| ------ | ------ | ------------------------------------------------- |
150 -| Write | `POST` | `/tool_router/session/{session_id}/execute` |
151 -| Write | `POST` | `/tool_router/session/{session_id}/execute_meta` |
152 -| Write | `POST` | `/tool_router/session/{session_id}/search` |
153 -| Write | `POST` | `/tool_router/session/{session_id}/proxy_execute` |
148 +| Access | Method | Route |
149 +| ------ | ------ | ------------------------------------------------ |
150 +| Write | `POST` | `/tool_router/session/{session_id}/execute` |
151 +| Write | `POST` | `/tool_router/session/{session_id}/execute_meta` |
152 +| Write | `POST` | `/tool_router/session/{session_id}/search` |
153
154 For [session-linked MCP access](/docs/sessions-via-mcp), use `session.mcp.url` and `session.mcp.headers` unchanged. `POST` requests require Session tool execution with Write only access. The transport does not support `GET` (SSE) or `DELETE`; granting additional permissions does not enable those methods.
155
@@ -253,7 +252,7 @@ Execute predefined Composio tools.
252
253 Execute raw proxy requests against connected accounts.
254
256 -Proxy execute is separate from tool execution. Grant it only when your application needs to call a connected account API through the raw proxy path.
255 +Proxy execute is separate from tool execution and from Session tool execution. It is the only permission that grants the session proxy route below, whether the call comes from `session.proxyExecute()` or from code running in that session's sandbox. Grant it only when your application needs to call a connected account API through the raw proxy path.
256
257 | Access | Method | Route |
258 | ------ | ------ | ------------------------------------------------- |
docs/kb/articles/platform-project-api-key-permissions.md
+1 -1
@@ -21,4 +21,4 @@ Create a correctly scoped Project API key or use an appropriate full-access Proj
21
22 ## Session tool execution requires write access
23
24 -Set **Session tool execution** to Write to search and execute tools through a session or its MCP server. This permission also covers session proxy requests and allows the key to invoke any tool exposed by the session-linked MCP server.
24 +Set **Session tool execution** to Write to search and execute tools through a session or its MCP server. This permission allows the key to invoke any tool exposed by the session-linked MCP server. It does not cover session proxy requests; those need **Proxy execute**.