Agent capabilities
Capability controls
Control which built-in tools an organization permits and let members narrow their own surface.
Capability controls apply to built-ins—media, web, and memory—not to OAuth connectors. Connecting or disconnecting an account is already the connector's switch.
Control surfaceDashboard → CapabilitiesBuilt-ins default on; explicit settings narrow visibility
Two levels, one effective result
effective capability = organization enabled AND member enabled- The organization setting is the ceiling. A member cannot turn on a capability that the organization disabled.
- A member can narrow an organization-enabled capability for themselves.
- No stored setting means enabled; only deviations from the default need to be recorded.
- Member settings are scoped to
(member × organization), never to a global user profile.
What disabling changes
Disabling a built-in unregisters its tools from the caller's /mcp surface.
The tools disappear from tools/list instead of remaining visible and failing
only at execution time.
For memory, disabling affects tool visibility only. Existing memories remain stored until the user explicitly deletes them in the Memory UI.
API-key-specific capability allowlists are not part of v0. The current hierarchy is organization plus member.