MCP Tools

The MCP tool surface is split into nine purpose-scoped endpoints. Each endpoint groups tools by workflow so an agent only loads what it needs. A simple retrieval agent connects to Vault Core and sees 18 tools costing ~3K context tokens. A compliance auditor adds Audit & Intelligence for ~6K total. The full surface is still available via a legacy single-endpoint connection for agents that need everything.

Endpoint boundaries align with Shield capability classes. An agent that only connects to read-only endpoints cannot accidentally invoke write or economy-mutating tools because those tools are not in its MCP tool list. Shield still enforces at the request level, but the endpoint topology adds defence in depth.

Every tool has exactly one canonical home. Aliases (get_balance/get_credit_balance, get_escrow_holds/get_credit_escrow) are retired to a single canonical name. Five tools are intentionally dual-registered where distinct workflows both need them — these are read-only and stateless. A lightweight discovery endpoint (/mcp/discover) returns the full endpoint manifest so agents can self-select before connecting.