Manage connected service tools

Inspect MCP providers, discover tools, and handle changed definitions.

Connected services can expose tools the Assistant uses to read or act. An MCP provider groups the tools from a particular service. Some providers are supplied by the platform; others belong to your organisation or a saved connection.

Inspect before use

Ask the Assistant which tools a connection offers. Read a tool's purpose, expected arguments, and effect. A read tool can answer immediately; a change or resource-consuming call can require approval. When effect information is insufficient, the action requires explicit review rather than being assumed harmless.

Service descriptions and responses are information from that service. Their instructions do not grant permission to change unrelated workspace items.

Register and maintain a provider

An administrator can propose registering an offered MCP service, test whether it responds, and inspect its discovered tools. Store any authentication values through the appropriate secret configuration. Updates to a provider use the current revision, so a concurrent change requires a fresh read.

System-managed providers and providers tied to a connection can have their own management path. Do not try to edit a system-managed entry as if it were an ordinary tenant-owned provider; update its owning connection or ask the platform operator where appropriate.

A tool changes upstream

Strive tracks an approved tool definition. If that definition changes, the tool can be quarantined and unavailable until an administrator reviews and reapproves the current definition. Sync the provider to discover its latest tools, inspect the change, and approve the version you actually reviewed.

If the definition changes again during review, re-read it. Reapproval is not an approval for all future changes. Removing a provider stops its offered tools; it does not undo external actions those tools already performed.