DCL Trust Oracle — AI/LLM Output Audit (x402 MCP)

There is meaningful overlap among the many dcl_evaluate_* variants (e.g., fast/strict/jailbreak/safety, secrets/wallet/pii, mev/signal/trade), so an agent could easily pick the wrong one. The descriptions are detailed and do help, but the boundaries between policies are subtle enough that the set is not clearly disambiguated.

The dcl_evaluate_* family is highly consistent, and the remaining tools (dcl_commit, dcl_audit_decode, dcl_audit_decode_deep, dcl_pipeline_start) still follow the same snake_case dcl_ prefix convention. Minor deviations like using adjectives/adverbs in evaluate_fast/strict and noun-verb ordering in dcl_pipeline_start keep it from a perfect 5.

18 tools is on the heavy side, especially since many are single-policy evaluators that could arguably be consolidated behind a policy parameter. That said, the tool count is justified by distinct pricing tiers and the breadth of audit categories, so it is borderline rather than excessive.

The audit lifecycle is well covered: pre-action evaluation, post-action scans, sanitization, final commit, and on-chain retrieval/verification. Minor gaps exist—no list/query tool for the append-only chain and no way to define custom policies—but the core workflows have no dead ends.