Tool policies
Native Tools (web search, image generation, and future platform tools) extend chat. The Native Tool Invocation Policy lets owners and admins control which Native Tools are available, how they run, and which Tool backends are ordered for each tool — for the active context.
This is separate from future externally connected tools (MCP).
Where to configure
Open Settings → Native Tools while the context you want to configure is active in the organization switcher.
- Personal (Individual) — you manage your own Native Tools policy.
- Organization — owners and admins manage policy for all members. Members can use tools allowed by policy but cannot change organization-wide settings.
What you can control
Policy settings apply across the active context:
- Enable or disable Native Tools — turn specific tools on or off in the workspace catalog.
- Approval requirements — operating mode (for example require approval before a tool runs). Modes that a backend does not support are called out on that backend in settings.
- Ordered Tool backends — for each Native Tool, enable and order backends (for example Gateway Perplexity, then a private SearXNG). The first backend that is allowed for the current chat provider and Environment class is used. See Web Search and Image Generation.
- Environment class — each backend shows the Environment class inherited from its provider connection. Higher-E chat providers will not use lower-E backends.
- Shared and backend-specific options — for example max results for search, or model on an image backend.
Individual conversations can enable or disable Native Tools from the chat header within what policy allows. Members do not pick which backend runs; the tools popover can show which backends are eligible under the current chat provider. If no backend is eligible, the tool stays visible but disabled with a short reason.
If a tool is disabled in policy, members cannot turn it on in chat.
Audit log
Changes to Native Tools policy are recorded in the audit log on the same page. Owners and admins can review who changed settings and when. See Audit logs.
Related pages
- Chat basics — using tools during a conversation
- Members, roles & invites — who can manage settings
- Provider environment — Environment class (E-class)
- Data routing policy — separate from tools; controls provider routing for content sensitivity