The outcome

Expose an agent or tool without leaking personal tokens, confusing tenant authority, mishandling end-user data, or allowing replayed side effects.

Coze is a visual platform and API for building, evaluating, publishing, and operating AI agents, workflows, knowledge, plugins, tools, and multi-channel applications. Composing and publishing AI agents and workflows with prompts, models, knowledge, variables, plugins, APIs, and channel integrations without building every orchestration surface from scratch. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Map end users, developer workspace, agent, OAuth app or personal token, plugin API, third parties, data fields, permissions, notices, consent, side effects, quotas, retention, and incident owners.

  2. 02

    Prefer OAuth or dedicated scoped service credentials for production, keep every secret server-side, separate environments and tenants, set expiry and rotation, and never share one personal token across users.

  3. 03

    Validate signatures and schemas, canonicalize identifiers and URLs, bind requests to the authenticated user and tenant, enforce authorization at the plugin API, and reject unknown fields and destinations.

  4. 04

    Make writes idempotent, require confirmation for messages, publication, purchases and account changes, use timeouts and rate limits, redact logs, and return bounded responses with no credentials or excessive records.

  5. 05

    Test token leak and revocation, forged identity, tenant crossover, prompt injection, SSRF, replay, duplicate calls, timeouts, credit exhaustion, consent withdrawal, deletion and rollback before canarying.

Working standard

What good use looks like.

  • Keep all Coze tokens server-side.
  • Authorize at the plugin service.
  • Make external writes idempotent.

Coze agents can combine third-party models, plugins, APIs, knowledge, and publishing channels, so every component adds separate data terms and trust boundaries. Coze warns against exposing personal access tokens in browser code, places end-user notice and consent duties on developers, and requires lawful handling of plugin requests and protected information. Minimize shared data, review every third party, scope credentials, validate and reauthorize tool calls, make writes idempotent, require approval for consequential actions, publish privately first, and support correction, export, revocation, and deletion.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.