Please explain the motivation behind the feature request.
There are a few newer sets of tools that are built in, but not surfaced as MCP extensions meaning they cannot be disabled at all.

Describe the solution you'd like

• The manage extensions set definitely needs to be able to be disabled, to support workloads where goose should use only the extensions explicitly enabled.
• The parallelism sub agent tool
• The todo list manager tool set

These can default to enabled, like the dev toolkit, but should at minimum be controllable by the user like all other tools.

I also think it'd be a good decision to adopt that goose will never build in tools that cannot be disabled by the user. Trust Trust Trust.

Describe alternatives you've considered
There's a tool set permissions config, but that seems like the wrong solution, since its counter to how I'd expect to interact with these tool sets, which would be the same as all other extensions including the enabled by default developer built in.

• I have verified this does not duplicate an existing feature request