Tool policies

Under Organization settings → Tools & integrations → Tool policies you set rules for your organization's tools: what happens to integrations DeutschlandGPT publishes in future, and which tools members may connect themselves. You need the permission Manage organization settings. Every switch takes effect as soon as you change it.

Which integrations exist today and who may use them is set under Integrations. That page also shows the current position of the new-integrations switch and links here.

Enable new integrations automatically

Enable new integrations automatically controls what happens to an integration DeutschlandGPT publishes in future.

• On (default): a newly published integration is available to your organization right away. If you do not want it, switch it off afterwards under Integrations.
• Off: a newly published integration starts blocked and only becomes usable once an administrator releases it under Integrations.

Switching this off is not retroactive. Every integration available to your organization at that moment stays enabled, including ones you never released explicitly; from then on they count as explicitly released. If you switch it back on later, those releases and everything you have set per integration since stay as they are.

Your organization's own connections, such as an MCP server or WebDAV server you added yourself, are exempt and work immediately.

Allow local MCP servers

Allow local MCP servers decides whether members may add MCP servers in the desktop app that run on their own computer and are used by Code and Cowork. The switch is on by default. Every call runs with the member's rights on their device, and the results go to the selected AI model. When you switch it off, the desktop app stops all local servers at its next sync. Details are under Local MCP servers.

The switch only appears when local MCP servers are enabled for your organization.