Private preview · public architecture
Inspect the curated tool boundary
See the small, declared tool catalogue a client may request without creating an MCP session or invoking a tool.
Browse only. No account data, credential, MCP session, or product runtime is contacted here.
Public contract example
A model sees a curated capability, not your entire system
The public catalogue shows a deliberately narrow set of methods; a visible method is not an open grant or an executed tool call.
Representative Workflows MCP examples
| Tool | Public meaning | Private workflow scope | Boundary |
|---|---|---|---|
| nodeTypes.list | Inspect the reviewed workflow node catalogue. | Read workflows | Curated before a client can invoke it |
| workflows.compose | Propose a workflow plan inside the declared boundary. | Edit workflows | Curated before a client can invoke it |
| connectors.list | Discover declared connections after a private grant is in place. | Read workflows | Curated before a client can invoke it |
What this surface owns
A specific boundary, not a generic feature list
The public record shows the contract a buyer can inspect. Configuration, credentials, and effectful actions remain inside a provisioned workspace.
- 01Public reference
Curated capability catalogue
Expose only reviewed tool shapes that are appropriate for a client connection.
Use MCP
- 02Private workspace
Workspace-bound authorization
Bind a grant to its organization, project, environment, audience, and expiration.
Use MCP
- 03Private policy
Effect-aware execution
Keep a consequential action behind its own confirmation and product policy.
Use MCP
The suite