Skip to main content

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

Private preview

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

ToolPublic meaningPrivate workflow scopeBoundary
nodeTypes.listInspect the reviewed workflow node catalogue.Read workflowsCurated before a client can invoke it
workflows.composePropose a workflow plan inside the declared boundary.Edit workflowsCurated before a client can invoke it
connectors.listDiscover declared connections after a private grant is in place.Read workflowsCurated before a client can invoke it
Public to inspect

A tool name, schema boundary, scope, and effect posture can be inspected before access is granted.

Private to provision and run

Client grants, workspace resources, and tool invocation remain authenticated and policy-bound.

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.

  1. 01

    Curated capability catalogue

    Expose only reviewed tool shapes that are appropriate for a client connection.

    Use MCP

    Public reference
  2. 02

    Workspace-bound authorization

    Bind a grant to its organization, project, environment, audience, and expiration.

    Use MCP

    Private workspace
  3. 03

    Effect-aware execution

    Keep a consequential action behind its own confirmation and product policy.

    Use MCP

    Private policy