Security and capability boundaries

资料正文

§1 Credential handling

Data	Handling
OAuth access and refresh tokens	Stored only in macOS Keychain or Windows CurrentUser DPAPI; not written to profile metadata.
Profile metadata	Stored locally and may include non-secret account, site, scope, and expiry metadata.
App key	A public identifier that may be used as explicit context. It is not an App Secret.
App Secret, cookies, auth codes, PKCE verifiers	Must never be pasted into prompts, committed, logged, or included in feedback.

§2 Execution boundaries

devapi call uses fixed method, path, and input declarations. Secret-bearing response fields are removed recursively.
auth request is a diagnostic escape hatch for a known existing route. It must not be used to bypass an allowlist.
Sandbox account deletion is excluded and must not be recreated with a raw request.
Use read-only checks by default. Ask for explicit approval before a write action.
Generated code and explanations still require developer review, tests, and production validation.

§3 Capability boundary

📌 This documentation covers capabilities available in the current published CLI and bundled skills: skill distribution, developer-source guidance, Partner Center OAuth profiles, App and sandbox context, fixed DevAPIs, supported OpenAPI proxy workflows, local hooks/history, diagnostics, and updates. Do not treat roadmap items as available. If a command is not shown by the installed tts_open_toolkit --help or current release notes, describe it as unavailable or planned.

§4 AI output boundary

The Toolkit reduces unsupported guesses by giving the agent structured TikTok Shop context and fixed operations. It does not replace code review, API response evidence, security review, or business acceptance testing.

§5 Was this page helpful?

Was this page helpful?

Tell us what worked, what was unclear, or what should be added. TTS Open Toolkit Feedback Form