Tools Catalog
During a turn the agent can call tools. AiHummer ships a built-in tool runtime: some tools are on by default, others activate only when you provide the required configuration. Tools are SSRF-guarded and sandboxed where relevant, and risky tools can be put behind a human approval gate.
Enabled by default
These tools work out of the box (some depend on a configured model or knowledge base).
| Tool | What it does | How to enable |
|---|---|---|
web_fetch |
Fetch the contents of a URL. SSRF-guarded. | On by default |
http_request |
Make an outbound HTTP request. SSRF-guarded. | On by default |
doc_generate |
Generate documents (CSV / TSV / XLSX). | On by default |
image_generate / edit_image |
Generate or edit images. | On by default |
github_get_file |
Fetch a single file from a GitHub repository. | On by default |
generate_pairing_code |
Issue a device pairing code. | On by default |
search_knowledge |
Search the knowledge base (RAG) and ground answers with citations. | With a knowledge base configured |
deep_research |
Run multi-step research and produce a cited report. | On by default |
docs_search |
Search an offline copy of this documentation (a docs.aihummer.ru snapshot ships in the release, share/docs, ru/en) — the agent can answer product questions without internet. |
With the docs snapshot present (standard install) |
docs_read |
Read a full documentation page found via docs_search. |
With the docs snapshot present (standard install) |
Enable on configuration
These tools stay off until you point them at the resource they need. All the
enabling knobs (SEARXNG_URL, CLOAKBROWSER_CDP_URL, AIHUMMER_FS_ROOT,
AIHUMMER_DB_QUERY_DSN, AIHUMMER_CODE_EXEC, …) are Settings-catalog keys:
set them in the web admin UI (Management → Settings, it has search) or with
aihummer settings set <KEY> <VALUE>. Putting them in gateway.env has no
effect — the environment is ignored for these keys.
| Tool | What it does | How to enable |
|---|---|---|
web_search |
Search the web. | SEARXNG_URL (SearXNG instance) |
browser / computer |
Drive a real browser via the Chrome DevTools Protocol. | CLOAKBROWSER_CDP_URL (CDP, default port :9222) |
filesystem_read |
Read files, sandboxed under a root directory. | AIHUMMER_FS_ROOT |
db_query |
Run read-only SQL queries. | AIHUMMER_DB_QUERY_DSN |
mail |
Send and read email. | SMTP / IMAP credentials |
tts |
Synthesize speech (text-to-speech). | AIHUMMER_TTS_URL (TTS sidecar) |
code_exec |
Execute code in a sandbox. | AIHUMMER_CODE_EXEC |
[!DANGER]
code_execis off by default on shared hosts. Only enable it in an environment you control and trust, because it runs model-authored code. Even sandboxed, treat it as a privileged capability.
Integration tools
When the matching connection is configured, the agent also gets domain tools:
| Tool | What it does | How to enable |
|---|---|---|
| Bitrix24 CRM / task / calendar tools | Read and act on Bitrix24 CRM records, tasks and calendar. | Bitrix24 connection configured |
| 1C (БИТ.ФИНАНС OData) | Query 1C accounting data over the БИТ.ФИНАНС OData interface. | 1C OData connection configured |
Approval gate
Any tool can be put behind a human-in-the-loop approval gate. List the tool
names in the AIHUMMER_APPROVAL_TOOLS setting (web admin UI: Management →
Settings); before such a tool runs, an operator must approve the call. A
rejected call is not executed.
aihummer settings set AIHUMMER_APPROVAL_TOOLS mail,code_exec
Air-gapped mode
Set the AIHUMMER_AIRGAPPED setting to 1 to block model-controlled public
egress. In this mode the agent cannot reach the open internet through tools,
which is appropriate for sovereign or isolated deployments.
aihummer settings set AIHUMMER_AIRGAPPED 1
[!NOTE] Beyond the built-in catalog, AiHummer can synthesize tools from any OpenAPI 3.x spec and expose any MCP server’s tools with no integration code. See the Marketplace & Plugins section of the docs.
Where to next
- The variables referenced here in full: Environment variables.
- Manage the running instance: CLI reference.