Skip to main content
Multi-environment agent setups create tool conflicts when different capabilities overlap or shadow each other. HERMES_ONLY_TOOLS provides deterministic tool filtering for production deployments.
The user runs a multi-tool agent; HERMES_ONLY_TOOLS keeps the exposed tool set deterministic.

Quick Start

1

Basic Filtering

Filter to specific tools in multi-env setups:
2

Multi-Environment Setup

Prevent tool shadowing in complex environments:

How It Works


Configuration Options

Environment Variable Format

Discovery Commands

Check tool filtering status:

Common Patterns

Pattern 1: Environment-Specific Filtering

Pattern 2: Capability-Based Filtering

Pattern 3: Incremental Rollout


Best Practices

HERMES_ONLY_TOOLS requires exact spelling matching registration names. Typos silently drop tools from availability.
Environment variables must be set before creating agents. Runtime changes don’t affect existing agents.
Log or validate that required tools are available after filtering to catch configuration issues.
HERMES_ONLY_TOOLS is designed for production where deterministic behavior is critical. Consider cost, security, and reliability implications.

Troubleshooting

Missing Tool Errors

When agents try to use filtered tools:
Solutions:
  1. Add missing tool to whitelist: "web_search,send_email"
  2. Update agent instructions to use only available tools
  3. Check tool name spelling in whitelist

Tool Discovery Issues

Name Matching Failures

Common tool name variations that cause mismatches:

Decision Guide

Choose the right filtering approach:

Tools Overview

Core tool system concepts

Agent Configuration

Agent setup and configuration