Tools Catalog

aihummer settings set AIHUMMER_APPROVAL_TOOLS mail,code_exec

aihummer settings set AIHUMMER_AIRGAPPED 1

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 | | `web_search` | Search the web through the built-in SearXNG. | On by default (bundled with the installer); turn it off with `--no-search` | | `browser` / `computer` | Drive a real browser via the Chrome DevTools Protocol. | On by default (bundled with the installer); turn it off with `--no-browser` | | `memory_store` | Store a fact in long-term memory (Einstein). With capture mode `auto` (the default) the fact is searchable immediately; with `review`/`off` it becomes a candidate awaiting approval. The result carries a `searchable_now` field. | On by default | | `memory_search` | Search long-term memory (Einstein). | 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) | | `filesystem_read` | Read a file or list a directory on the server's disk. | **Always on.** `AIHUMMER_FS_ROOT` does not switch it on — it only **narrows** the sandbox: while the value is empty the sandbox root is the whole server (`/`). | > [!DANGER] > **What happens:** the agent reads any file the gateway service user can read — > including the file holding your database connection details and the key that > encrypts the secret store. > **Under what condition:** while the `AIHUMMER_FS_ROOT` setting is empty. That > is the default state right after a self-hosted install. > **How to fix it:** open **Management → Settings**, find `AIHUMMER_FS_ROOT`, > point it at the directory the agent actually needs (for example > `/srv/agent-files`) and save. The value lives in the database — a line in > `gateway.env` is ignored for this key. Additionally list `filesystem_read` in > `AIHUMMER_APPROVAL_TOOLS` so every call waits for your approval. > > On AiHummer managed cloud the tool is not given to the agent at all — you only > need to narrow the root on your own installation. ## Enable on configuration These tools stay off until you point them at the resource they need. All the enabling knobs (`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 | |---|---|---| | `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_exec` is **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. ```bash 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. ```bash 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](/en/v1.0/reference/env-vars). - Manage the running instance: [CLI reference](/en/v1.0/reference/cli).