Account and secret controls
Credential tools change saved account or environment state. Prefer the private UI fields so secrets never enter chat history. No tool on this page reveals a stored secret value. Process environment availability and connected-account identity are separate concepts.
set_my_composio_token
Section titled “set_my_composio_token”Save the requester’s personal Composio consumer key.
| Argument | Required | Meaning and default |
|---|---|---|
token |
Yes | Token text; trimmed value must have at least six characters. |
Authority and scope: Verified trusted person; affects only their Composio user identity.
Result: Saved confirmation without token echo.
Restrictions: Prefer private credential forms. If this chat tool is used, send the credential in a DM and delete the source message immediately; the tool cannot erase Slack history. API attribution is not a verified personal principal.
clear_my_composio_token
Section titled “clear_my_composio_token”Remove the requester’s personal Composio key.
Arguments: none.
Authority and scope: Verified trusted person, personal scope.
Result: Removal confirmation.
Restrictions: Also revokes active daemon remote-MCP author relays so a removed token stops working; shared credentials remain unchanged.
set_my_toolbox_token
Section titled “set_my_toolbox_token”Save the requester’s personal Toolbox bearer token.
| Argument | Required | Meaning and default |
|---|---|---|
token |
Yes | Trimmed token of at least six characters. |
Authority and scope: Verified trusted person; personal Toolbox credential.
Result: Saved confirmation without token echo.
Restrictions: Use a DM and delete its source message if this chat path is used. The connected server determines account permissions.
clear_my_toolbox_token
Section titled “clear_my_toolbox_token”Remove the requester’s personal Toolbox credential.
Arguments: none.
Authority and scope: Verified trusted person, personal scope.
Result: Removal confirmation.
Restrictions: Revokes the author’s active remote-MCP relay registrations; conversation/organization fallback credentials are independent.
list_secrets
Section titled “list_secrets”List configured environment secret metadata without values.
| Argument | Required | Meaning and default |
|---|---|---|
scope |
No | all (default), organization, personal, conversation; aliases org, my, channel. |
Authority and scope: Admitted current conversation; personal details require a verified author, organization masked tails/setter details require admin.
Result: Names, providers, protection/exposure/host state, resolvability and authorized masked metadata by scope.
Restrictions: Never returns raw values. Effective precedence is conversation over personal over organization. Listings are live; an already-running process retains its start environment. Strict runtime guard can withhold readable/unprotected secrets.
set_secret
Section titled “set_secret”Write a personal or organization environment secret.
| Argument | Required | Meaning and default |
|---|---|---|
name |
Yes | Environment-variable name; validated and normalized by storage. |
value |
Yes | Secret value; never returned. |
scope |
No | personal (default), organization; aliases my, org. |
hosts |
No | Up to 16 declared destination patterns; omitted preserves existing rule choice. |
mode |
No | auto, hidden, readable; new entries default auto, omitted on updates preserves choice. |
headers |
No | Up to 8 supported credential header names; optional. |
format |
No | bearer, raw, basic-password, basic-user; optional credential-format rule. |
Authority and scope: Verified self for personal; administrator for organization, subject to scope-dependent approval policy.
Result: Saved name and protection state, without value.
Restrictions: Conversation values use its Variables/Secrets form or admin UI. Never paste into a shared channel. Built-in and declared HTTPS rules determine placeholder use; broad multi-tenant destination suffixes are refused. Delete a chat credential source message after saving.
remove_secret
Section titled “remove_secret”Remove an environment secret entry.
| Argument | Required | Meaning and default |
|---|---|---|
name |
Yes | Variable name. |
scope |
No | personal (default), organization; aliases my, org. |
Authority and scope: Verified self for personal; administrator for organization; scope-dependent approval applies.
Result: Removed-name confirmation.
Restrictions: Conversation entries are managed through their private form. Other scopes remain; in-flight processes retain their existing environment.
set_secret_mode
Section titled “set_secret_mode”Change hidden/readable exposure without changing its value.
| Argument | Required | Meaning and default |
|---|---|---|
name |
Yes | Existing secret name. |
mode |
Yes | hidden, readable, or auto. |
scope |
No | personal (default), organization, conversation; aliases my, org, channel. |
Authority and scope: Verified self for personal; administrator for organization; conversation manager/admin for conversation. For personal readable, the control-plane gate also requires an administrator; personal hidden/auto stays the owner’s call.
Result: Resolved exposure and destination metadata; next-process effect.
Restrictions: Hidden requests carry placeholders; readable is for non-HTTPS use, subject to the strict runtime guard. Declared/known destination rules and automatic non-HTTPS recognition still apply. Existing process env is unchanged.
allow_secret_host
Section titled “allow_secret_host”Approve an exact host for a hidden secret awaiting destination approval.
| Argument | Required | Meaning and default |
|---|---|---|
name |
Yes | Existing secret name. |
host |
Yes | One hostname, no wildcard. |
scope |
No | personal (default), organization, conversation; aliases my, org, channel. |
Authority and scope: Organization administrator acting from the conversation chat; scope access is checked too.
Result: Approved-host confirmation or note that known/declared rules still govern this entry.
Restrictions: Model API hosts are refused. Does not enable arbitrary network access or override known destination restrictions. Useful when a background job/SSH request posted no approval card.
Related guides
Section titled “Related guides”Accounts, environment configuration, secrets, Composio SDK, and Toolbox/Make.