Skip to main content

Manage Toolsets

Tasks

Curate named tool sets once and attach them to any binding. For the model behind Toolsets, see Toolsets.

Create a Toolset​

  1. Go to Inventory → Toolsets → New Toolset.

  2. Give it a name and description, then add tool rows. Each row names servers and tools:

    To expressServersTools
    Two tools on one servergithub-mcpget_issue, list_pull_requests
    Every read-style tool everywhere*read_*

    The drawer shows a live matches N tools count against the current inventory as you edit.

  3. Save. The Toolset appears in the library with its match count and the bindings that reference it.

Attach a Toolset to a binding​

  1. Edit an Access Binding (Setup → Settings → Access Bindings).
  2. In the Toolsets field, select one or more toolsets. Their tools join the binding's own grant.
  3. Save. The compiled-policies preview reflects the referenced toolsets' selectors — the same policies that enforce at runtime.
note

A toolset referenced by any binding — enabled or disabled — can't be deleted or renamed until you detach it: a delete must never silently shrink a grant, and disabling a binding is not enough. Remove the reference from every binding that names the toolset to free it.

Override a tool's description​

A Toolset can replace the description a tool advertises to the model — useful for normalizing verbose upstream text or masking a description that has drifted. The override is presentation-only: the tool's name, routing, policy, and audit records are unchanged. Add an override entry naming the server, the tool, and the replacement description.

Build a Toolset from usage​

The least-privilege shortcut: from an agent or team's activity, propose a Toolset containing exactly the tools that identity called recently. Review the proposal, save it as a Toolset, attach it to a binding, then set the server's unlisted-tool posture to deny — everything the identity never used is now denied.

See also​

Last updated on