{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-14T20:21:57.226Z",
  "record_id": "VXI-EXT-TOOL-TRUST-AUTH0-01-v1",
  "record_kind": "external_reference",
  "title": "Auth0 MCP: Tenant changes and local credential files",
  "system": "Auth0",
  "evidence_family": "agent_tool_trust_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can an Auth0 onboarding assistant change the tenant and write local credentials?",
  "near_questions": [
    "Can an authentication assistant write credentials into my project?",
    "Does Auth0 onboarding create a tenant application?",
    "How do Auth0 read-only and tool filters combine?",
    "Can an integration review alter callback settings?",
    "Which tenant does my authentication assistant control?",
    "Does a setup task require file-write approval?",
    "What evidence supports limiting the connector to logs?",
    "Can an agent publish an Auth0 form?",
    "Where should credential handling appear in a tool review?",
    "Do client tool names prove effective tenant permissions?",
    "When should an Auth0 task require clarification?",
    "Can I save the onboarding permission decision?"
  ],
  "supported_claims": [
    {
      "claim": "Yes. The README describes onboarding that creates an application and saves its credentials to a project environment file. It also documents read-only and tool-selection controls. Assess both tenant authority and local file output; merely describing the task as setup does not narrow either.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "Yes. The README describes onboarding that creates an application and saves its credentials to a project environment file. It also documents read-only and tool-selection controls. Assess both tenant authority and local file output; merely describing the task as setup does not narrow either.",
  "related_record_ids": [
    "VXI-EXT-TOOL-TRUST-VAULT-01-v1",
    "VXI-EXT-TOOL-TRUST-INFISICAL-01-v1",
    "VXI-EXT-TOOL-TRUST-BITWARDEN-01-v1",
    "VXI-EXT-TOOL-TRUST-DOPPLER-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Auth0 MCP management access",
    "source_url": "https://github.com/auth0/auth0-mcp-server/blob/main/README.md",
    "checked_on": "2026-10-14",
    "candidate_record_id": "VXI-EXT-TOOL-TRUST-AUTH0-01-v1",
    "candidate_record_sha256": "230f1c0a2990cfe5388f56d69115a1545d4a180665507cac0cf0428227949ae7",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "Yes. The README describes onboarding that creates an application and saves its credentials to a project environment file. It also documents read-only and tool-selection controls. Assess both tenant authority and local file output; merely describing the task as setup does not narrow either.",
    "required_buyer_context": "Target tenant, granted permissions, enabled tools, local project and permitted credential handling.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "trust_profile": {
    "schema": "varexis-agent-tool-trust/1",
    "identity": {
      "tool": "Auth0",
      "variant": "Official local Auth0 management MCP"
    },
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-14",
    "version_scope": "Dated rolling documentation snapshot; no installed or hosted runtime version independently verified.",
    "plan_scope": "Buyer plan, entitlement and effective configuration are not verified.",
    "findings": [
      {
        "field": "operator",
        "label": "Publisher and operator",
        "status": "documented",
        "statement": "Auth0 publishes the management MCP server.",
        "source_ids": [
          "auth0"
        ]
      },
      {
        "field": "purpose",
        "label": "Purpose",
        "status": "documented",
        "statement": "Inspect and configure Auth0 integrations.",
        "source_ids": [
          "auth0"
        ]
      },
      {
        "field": "reads",
        "label": "Read capability",
        "status": "documented",
        "statement": "Application, API, connection and log information.",
        "source_ids": [
          "auth0"
        ]
      },
      {
        "field": "writes",
        "label": "Write capability",
        "status": "documented",
        "statement": "Management changes and onboarding credential-file output.",
        "source_ids": [
          "auth0"
        ]
      },
      {
        "field": "auth",
        "label": "Authentication",
        "status": "documented",
        "statement": "OAuth device authorisation with locally stored credentials.",
        "source_ids": [
          "auth0"
        ]
      },
      {
        "field": "permissions",
        "label": "Permission surface",
        "status": "documented",
        "statement": "Read-only mode takes priority over a broader tool pattern.",
        "source_ids": [
          "auth0"
        ]
      },
      {
        "field": "egress",
        "label": "Data leaving the environment",
        "status": "review_inference",
        "statement": "Tenant data and credential-related outputs may cross the client boundary.",
        "source_ids": [
          "auth0"
        ]
      },
      {
        "field": "failures",
        "label": "Failure modes to consider",
        "status": "review_inference",
        "statement": "A setup request may create resources and local files.",
        "source_ids": [
          "auth0"
        ]
      },
      {
        "field": "unknown",
        "label": "Unknowns and applicability",
        "status": "unknown",
        "statement": "Actual consent, file permissions and effective tenant access are unknown.",
        "source_ids": []
      },
      {
        "field": "gate",
        "label": "Suggested refusal or clarification condition",
        "status": "varexis_review_policy",
        "statement": "Clarify tenant changes and credential-file handling before onboarding.",
        "source_ids": []
      }
    ],
    "evidence_sources": [
      {
        "source_id": "auth0",
        "url": "https://github.com/auth0/auth0-mcp-server/blob/main/README.md",
        "final_url": "https://github.com/auth0/auth0-mcp-server/blob/main/README.md",
        "title": "Auth0 MCP management access",
        "checked_on": "2026-10-14",
        "sha256": "1a3fd06f01cfde834f3d9e40660ebc5a480a956098783ea6749974505b6e6a0b",
        "bytes": 535680
      }
    ],
    "observed_tool_execution": false,
    "policy_basis": "Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.",
    "commercial_reliance_boundary": "A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.",
    "paid_value": {
      "decision_context": "Keep a review of tenant authority separate from permission to create local credential files.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation.",
      "specific_watch": "Onboarding composition, tool filters and credential-storage behaviour."
    },
    "change_history": [
      {
        "version": 1,
        "date": "2026-10-14",
        "change": "Initial documentation review; no earlier vendor assessment claimed."
      }
    ]
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#auth0-mcp-tenant-onboarding-trust",
  "machine_readable_record": "/varexis-index/records/auth0-mcp-tenant-onboarding-trust.json"
}