Skip to main content

Overview

Custom connectors can expose tools to public visitors, subscribers, or internal staff. Use tool access metadata when a connector has a mix of safe intake actions and private admin actions. By default, connector tools are treated as public_safe. Predefined connectors are automatically tagged by BoostGPT. OAuth2 connectors are public-safe because each subscriber authorizes their own account. For owner-token connectors, intake actions like creating a lead, booking a call, or adding a subscriber can stay public-safe, while private reads, reports, deletes, account changes, payment operations, databases, devops, and arbitrary outbound messaging are staff-only.

Access Levels

Tool Definition

Set access on each tool:
Mark private tools as staff-only:
You can also use tool_access:
Or annotations:
boostgpt_access is also supported:

Practical Example

For a CRM connector:

Choosing Access

Use public_safe when the tool:
  • creates or updates data for the current visitor
  • submits an intake form
  • books a meeting
  • sends a notification to the agent owner/team
  • does not reveal private account data
Use staff_only when the tool:
  • lists, searches, or exports private records
  • reads inboxes, channels, dashboards, reports, customers, or files
  • updates or deletes existing business records
  • sends messages to arbitrary recipients
  • changes account, billing, pipeline, or workspace settings

Notes

Tool access is enforced in two places:
  • hidden from the agent when the current chatter is not allowed to use it
  • blocked at execution if an old or forged tool call tries to run it
Access is based on capability and data scope, not only on whose API token the connector uses.