Tool registry

Agents in Zahen can only call tools that have been explicitly registered and enabled. The Tool Registry is where admins see every registered tool and control whether agents are permitted to use it.

What the registry shows

Each entry in the registry lists the tool’s name, a description of what it does, its current status (enabled or disabled), and whether it requires human approval before an agent may call it.

Screenshot

The Tool Registry page listing registered tools with their status toggles — added in a later docs update.

Enabling and disabling tools

Use the toggle next to any tool to enable or disable it. Disabling a tool takes effect immediately — if an agent has already planned to call that tool as part of a running task, the call will not go through. The task will pause or fail at that step rather than proceed with an unavailable tool.

This gives you a reliable kill switch if you need to pull a tool from use quickly.

Requiring human approval

Some tools touch sensitive systems or produce actions that are difficult to reverse. You can mark any tool as requiring approval, which means every planned call to that tool will pause and route to an approver before it executes — regardless of the task’s overall risk level. See Approvals for how approvers handle these pauses.

Note

Agents never hold tool credentials. When an agent calls a tool, the platform brokers the request: it retrieves the necessary credentials from a secure store, makes the external call on the agent’s behalf, and returns only the result. The agent itself never sees a secret or a raw credential. This is by design — it means a compromised or misbehaving agent cannot exfiltrate access to your external systems.

Who can access the registry

Platform admins have full access to the Tool Registry. Department admins can view enabled tools but cannot register new ones or change enabled/disabled status — contact your platform admin for those changes.