Two hundred tools including 'send campaign' is a lot of trust to hand a model. Klaviyo's answer is that the restriction lives in the connection rather than in a prompt: a client configured read-only cannot send, whatever it is asked. core-tools-only addresses the other problem — two hundred definitions in every request — by trimming to the common set. Restricting authorisation to Owner, Admin and Manager is the third layer, and the right one for a tool that can email a list.
Klaviyo's own endpoint, one of the largest surfaces here at roughly 200 tools across its documented categories. Crucially it ships connection parameters that cut that down.
- Campaigns — create, send and report
- Flows, segments and lists
- Profiles, including bulk import and merge
- Catalogs, email templates, events and metrics
- Coupons, forms and webhooks
- Connection parameters: read-only=true, core-tools-only=true, and toolset trimming
OAuth with dynamic client registration, and only Owner, Admin or Manager roles may authorise. Klaviyo also publishes a local server that takes a private API key.
Admin enables it, then paste and authorize — add the endpoint to your client, then approve the OAuth consent screen