Tool Permission Review with Claude Code: Result JSON Schema

A production playbook for tool permission review in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: Security reviewers for AI tools

The problem

Security reviewers for AI tools need tool permission review to run repeatedly against tool manifests, scopes, auth flows, and usage logs. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Define the outer result contract once, let the tool permission review skill own body.data, and reject terminal output that does not match the expected schema.

Tradeoffs and failure modes

Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For tool permission review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Result shape

{
  "schema_version": "argo.result.v1",
  "summary": "tool permission review completed",
  "body": { "type": "tool_permission_review", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo