Legal Due Diligence Document Review with Claude Code: MCP Tool Boundary
A production playbook for legal due diligence document review in legal operations using Claude Code: mcp tool boundary, run-scoped inputs, logs, typed results, and artifacts.
Audience: M&A legal teams and diligence operators
The problem
M&A legal teams and diligence operators need legal due diligence document review to run repeatedly against data room folders, contracts, corporate docs, schedules, and exception lists. In legal 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 legal due diligence document review, 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 legal due diligence document review, 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: legal-due-diligence_lookup
agent: Claude Code
input_scope: /skill/.argo/inputs
credential_owner: broker
log_arguments: true
network_policy: allowlisted
Run this on Argo