Skip to main content
Platform MCP Docs

Tools, Resources, and Approvals

Understand scoped capability discovery, strict arguments, safe resources, and proposal-first action classes.

Version MCP 2025-11-25 Current Streamable HTTP contract with compatibility versions Reviewed Jul 26, 2026 Next review Oct 26, 2026
Start Reading Report documentation issue Try in a Free Developer Workspace

The free Developer workspace is for non-production building and learning under published limits. External API or MCP client credentials use a separate scoped request and approval process.

Owner: Batoi Developer Experience Reviewed by: Batoi Platform Security Source revision: upgrade-jul-26-2026

Browse Batoi Platform MCP Documentation Tools, Resources, and Approvals
On this page

Tools, Resources, and Approvals

Tools

Every listed tool includes an input schema, annotations, action class, required capability, and an indication that no provider write is executed directly.

  • Read tools return bounded workspace-scoped projections.
  • Proposal tools create reviewable records only.
  • Approval-gated handoff tools queue an approval and provider handoff; they do not execute GitHub, SQL, deployment, or notification writes in the MCP request.

The server validates required fields, allowed top-level fields, types, limits, and enumerations before dispatch.

Resources

Approved resources currently include:

  • batoi://workspace/context for compact authenticated workspace identity and readiness.
  • batoi://workspace/capabilities for the host-filtered capability catalog.

Use resources/list before resources/read. Resource content is bounded and contains no bearer credential.

Approvals

Approval-required work pauses at a review boundary. An approval is narrow, versioned, expiring, revocable, and independently evidenced. MCP discovery or a model request does not constitute approval.