hermes - 💡(How to fix) Fix Feature: Per-tool enable/disable in config (below toolset granularity)

Problem

Currently, tool configuration only works at the toolset level. The web toolset bundles both web_search and web_extract — there's no way to enable one without the other via config.

A concrete example: users who have an MCP server for web scraping (e.g. fastcrw) may want the built-in web_search but NOT web_extract. The current workaround is setting web.extract_backend: '' so web_extract appears as a tool but fails harmlessly — which pollutes the tool list and wastes tokens on a useless schema.

Root Cause

The search toolset exists in TOOLSETS (toolsets.py) with only web_search, but it's missing from CONFIGURABLE_TOOLSETS (tools_config.py). Adding it there is a one-line fix for this specific case — but the broader issue remains: there's no way to disable a single tool from within a toolset via config.yaml.

Current State

• disabled_toolsets — disables entire toolsets ✅
• platform_toolsets — enables entire toolsets per platform ✅
• MCP servers support tools.exclude for per-tool filtering ✅
• Built-in tools: toolset-level only ❌

Proposed Solution

Add a config key for per-tool filtering that works alongside disabled_toolsets:

agent:
  disabled_tools:
    - web_extract       # disable just this tool
    - computer_use      # or specific tools from any toolset

Or alternatively, make toolset definitions more granular (split web into web_search and web_extract as separate toggles in CONFIGURABLE_TOOLSETS), so users can mix-and-match:

platform_toolsets:
  telegram:
    - search        # web_search only
    # no 'web'     # no web_extract

The search toolset already exists in TOOLSETS but just needs to be added to CONFIGURABLE_TOOLSETS to make this work.

Related

• MCP servers already support tools.exclude — built-in tools should have equivalent granularity
• Issue #21849 (Tool Permission Gating) is about runtime permissions, not config enable/disable