Change an integration connection's tool allow-list
Replaces the tools the organization’s agents may use through this built-in integration connection, validated against the catalog exactly as when the app was added: an empty list, an unknown tool, or a tool the read preset does not admit is refused. The connection’s state is unchanged. Every agent using the app inherits the new list at its next credential refresh. A connection that is narrowed at vault-grant time instead is refused with 422.
Authorizations
Headers
Path Parameters
Body
Request body changing the organization tool allow-list of a built-in, GitHub, or Slack integration connection. Validated against the provider's catalog; the connection's state is unchanged and sessions pick the new list up at their next credential refresh.
For a built-in integration, the permission preset the selected tools are checked against: read or write; when omitted, the read preset applies. Omit for native GitHub and Slack: GitHub tools determine token permissions; Slack tools do not change OAuth scopes or thread access.
The app's tools the organization's agents may use, by tool name from the catalog. Replaces the connection's allow-list in full; an empty list is refused. Omit to keep the current allow-list, for example to check a built-in integration's tools against another permission preset.
1 - 200 elementsResponse
OK
Lifecycle of the connection: pending was registered directly and waits for provider setup (a trust probe or registered OAuth sign-in activates it), active can mint tokens, suspended is restorable at the provider and resolves to no credential, revoked was uninstalled and must be installed again.