Board Deck Fact-Check with Claude Code: MCP Tool Boundary

A production playbook for board deck fact-check in cross-industry operations using Claude Code: mcp tool boundary, run-scoped inputs, logs, typed results, and artifacts.

Audience: Founder and finance teams

The problem

Founder and finance teams need board deck fact-check to run repeatedly against slides, metrics exports, source docs, and footnotes. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Expose only the MCP tools needed for board deck fact-check, validate tool arguments, keep credentials in the owning service, and log each call outside the sandbox.

Tradeoffs and failure modes

Narrow tool boundaries reduce agent flexibility, but make the integration reviewable and supportable. For board deck fact-check, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Tool policy

tool: board-deck-fact-check_lookup
agent: Claude Code
input_scope: /skill/.argo/inputs
credential_owner: broker
log_arguments: true
network_policy: allowlisted

Run this on Argo