Skip to main content

CrowdyStudioAgentCatalogTool

One implemented crowdy.agent-tools/1 tool, named exactly as a policy allowlist must name it.

type CrowdyStudioAgentCatalogTool {
  name: String!
  summary: String!
  executor: CrowdyStudioAgentToolExecutor!
  modes: [CrowdyStudioAgentMode!]!
  riskClass: CrowdyStudioAgentRiskClass!
  approvalRequired: Boolean!
}

Fields​

CrowdyStudioAgentCatalogTool.name ● String! non-null scalar​

Logical dotted tool name. This is the string an allowedToolNames entry must equal.

CrowdyStudioAgentCatalogTool.summary ● String! non-null scalar​

What the tool does, from its canonical descriptor.

CrowdyStudioAgentCatalogTool.executor ● CrowdyStudioAgentToolExecutor! non-null enum​

Trusted boundary that runs it: SERVER or BROWSER.

CrowdyStudioAgentCatalogTool.modes ● [CrowdyStudioAgentMode!]! non-null enum​

Modes the tool is available in.

CrowdyStudioAgentCatalogTool.riskClass ● CrowdyStudioAgentRiskClass! non-null enum​

Server-classified risk. Allowing the class is necessary but not sufficient: an approval-gated tool still requires exact human approval.

CrowdyStudioAgentCatalogTool.approvalRequired ● Boolean! non-null scalar​

Whether every call needs exact human approval regardless of policy.

Member Of​

CrowdyStudioAgentCatalog object