For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

An Action Gateway Toolbelt is a named, versioned group of tools. Use a Toolbelt to reuse a set of tools across sessions and apply a permission rule to the group instead of configuring every tool separately.

For example, an issue-triage Toolbelt can group tools for reading GitHub issues and updating Linear. It can span providers and include only the operations the agent needs. Toolbelts are optional. Select individual tools when you do not need a reusable group.

Toolbelts and Connections

A Toolbelt and a connection let you reuse different parts of an agent’s setup:

Two users can use the same issue-triage Toolbelt while each uses their own GitHub and Linear connections. Each session’s actor ID identifies whose connections to use. Reusing the Toolbelt does not share account access.

Toolbelt Selection and Permissions

Toolbelts serve three related purposes when creating a session:

• Tool selection: Include a Toolbelt to make its members available within the session’s selected tools.
• Group permissions: Set an allow, ask, or deny rule on the Toolbelt to apply that action to its member tools.
• Preloading: Preload a Toolbelt to expose its permitted member tools directly to the model, without requiring a search first.

These are separate settings. Selecting a Toolbelt does not automatically allow every member, and adding a policy rule does not make tools outside the session’s selection available. Preloading changes which definitions the client receives, not which calls it can make.

A Toolbelt rule provides a common permission for the group. More-specific rules can change the action for an individual tool or particular arguments. For example, allow a group of repository tools but require approval for a tool that posts comments. An ask rule requests approval for the individual call, not blanket approval for the Toolbelt. See Tool Policies for rule precedence.

Versions and Reuse

Reference a Toolbelt by name and version, such as toolbelt:research@1. The version identifies a fixed set of member tools. Publishing a newer Toolbelt version does not change the version selected by an existing session.

Use the same versioned reference in the session’s tool selection, group policy, and preload configuration when those settings should apply to the same members. To adopt a different membership, create a session that references the new version.

Tool Calls and Connections

A Toolbelt is not an executable workflow. The agent calls its member tools by their individual names, either directly, through Invoke Tool, or from Code Execution Tool.

Each call remains subject to the provider’s permissions, rate limits, and usage charges.

See Create Toolbelts to create a group and use it in a session.