Skip to main content
GET
JavaScript
Read one tool set secret, a secret scoped to a single tool set. You get its name and usage, never its value.
The toolsecret_... shape and the redacted value work exactly like a workspace secret; the difference is reach.

Scoped to one tool set, and it wins over workspace

A tool set secret is visible only to the tools in its own tool set, and it sits in the middle of the three-scope precedence: an objective secret beats it, and it beats a workspace secret of the same name. So a ${ORDERS_TOKEN} that this tool set should resolve differently from the rest of the workspace goes here. Confirm which scope a call used through resolvedSecrets on the tool call, where the source reads RESOLVED_SECRET_SOURCE_TOOLSET. Like the name, the external ID is normalized (hyphens and spaces to underscores), so externalId: "orders-tok" resolves as external_id:orders_tok.

Create a tool set secret

Add one, scoped to the tool set.

List tool set secrets

Every secret on this tool set.

Store and use secrets

The three scopes and how ${NAME} resolves.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

workspaceId
string
required

The workspace that owns the tool set.

Example:

"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"

toolSetId
string
required

The tool set the secret belongs to. Accepts the canonical ts_… form or the external_id: form.

Example:

"toolset_01HXKD2E5NQM3T9AYWCFNRMN74"

id
string
required

The secret to retrieve.

Example:

"toolsecret_01HXKD2E5NQM3T9AYWCF8PWC4R"

Response

OK

metadata
object
required

Standard metadata for persistent, named resources (e.g., agents, tools, prompts)

spec
object
required
info
object

Tool set secret information