{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-14T20:21:57.226Z",
  "record_id": "VXI-EXT-TOOL-TRUST-DOPPLER-01-v1",
  "record_kind": "external_reference",
  "title": "Doppler MCP: Read-only tools and token enforcement",
  "system": "Doppler",
  "evidence_family": "agent_tool_trust_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Do Doppler MCP scope flags enforce access beyond the connector?",
  "near_questions": [
    "Does a read-only connector flag restrict the underlying token?",
    "Can a secret-reading assistant attempt writes through another tool?",
    "Do Doppler project flags guarantee project isolation?",
    "Which permission boundary does the Doppler API enforce?",
    "Can read-only mode return secret values?",
    "What should procurement request about token scope?",
    "Is the Doppler MCP server described as experimental?",
    "Can a shared workstation reuse cached authentication?",
    "Which configuration identifies the intended secret environment?",
    "Does a hidden write tool mean no write authority exists?",
    "When should a broad secret token block approval?",
    "Can I save the token-versus-tool review?"
  ],
  "supported_claims": [
    {
      "claim": "The documentation distinguishes tool filtering from token-enforced API access. Read-only mode hides write tools, but does not stop other ways an agent might attempt writes. Project/config flags also are not a substitute for scoped credentials. Secret reads remain part of the advertised capability.",
      "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": "The documentation distinguishes tool filtering from token-enforced API access. Read-only mode hides write tools, but does not stop other ways an agent might attempt writes. Project/config flags also are not a substitute for scoped credentials. Secret reads remain part of the advertised capability.",
  "related_record_ids": [
    "VXI-EXT-TOOL-TRUST-VAULT-01-v1",
    "VXI-EXT-TOOL-TRUST-AUTH0-01-v1",
    "VXI-EXT-TOOL-TRUST-INFISICAL-01-v1",
    "VXI-EXT-TOOL-TRUST-BITWARDEN-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Doppler MCP tools and read-only mode",
    "source_url": "https://docs.doppler.com/docs/mcp",
    "checked_on": "2026-10-14",
    "candidate_record_id": "VXI-EXT-TOOL-TRUST-DOPPLER-01-v1",
    "candidate_record_sha256": "4cb86f3ae4fc83adff5ac1570396197a630f9170454b27befeff7f34fb3a8da6",
    "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": "The documentation distinguishes tool filtering from token-enforced API access. Read-only mode hides write tools, but does not stop other ways an agent might attempt writes. Project/config flags also are not a substitute for scoped credentials. Secret reads remain part of the advertised capability.",
    "required_buyer_context": "Token scope, project, config, client capabilities and approved secret disclosure.",
    "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": "Doppler",
      "variant": "Experimental local Doppler 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": "Doppler publishes the experimental MCP server.",
        "source_ids": [
          "doppler"
        ]
      },
      {
        "field": "purpose",
        "label": "Purpose",
        "status": "documented",
        "statement": "Secret, environment and configuration operations.",
        "source_ids": [
          "doppler"
        ]
      },
      {
        "field": "reads",
        "label": "Read capability",
        "status": "documented",
        "statement": "Secret values, configurations and activity information.",
        "source_ids": [
          "doppler"
        ]
      },
      {
        "field": "writes",
        "label": "Write capability",
        "status": "documented",
        "statement": "Secret and environment changes when permitted.",
        "source_ids": [
          "doppler"
        ]
      },
      {
        "field": "auth",
        "label": "Authentication",
        "status": "documented",
        "statement": "Interactive login or a runtime Doppler token.",
        "source_ids": [
          "doppler"
        ]
      },
      {
        "field": "permissions",
        "label": "Permission surface",
        "status": "documented",
        "statement": "API token permissions enforce access; connector flags narrow its exposed tools.",
        "source_ids": [
          "doppler"
        ]
      },
      {
        "field": "egress",
        "label": "Data leaving the environment",
        "status": "review_inference",
        "statement": "Readable secret values may reach the connected client.",
        "source_ids": [
          "doppler"
        ]
      },
      {
        "field": "failures",
        "label": "Failure modes to consider",
        "status": "review_inference",
        "statement": "A broad token can retain authority outside filtered MCP tools.",
        "source_ids": [
          "doppler"
        ]
      },
      {
        "field": "unknown",
        "label": "Unknowns and applicability",
        "status": "unknown",
        "statement": "Buyer token and other agent execution channels are unverified.",
        "source_ids": []
      },
      {
        "field": "gate",
        "label": "Suggested refusal or clarification condition",
        "status": "varexis_review_policy",
        "statement": "Do not claim enforced read-only access from a tool flag alone.",
        "source_ids": []
      }
    ],
    "evidence_sources": [
      {
        "source_id": "doppler",
        "url": "https://docs.doppler.com/docs/mcp",
        "final_url": "https://docs.doppler.com/docs/mcp",
        "title": "Doppler MCP tools and read-only mode",
        "checked_on": "2026-10-14",
        "sha256": "2aef28dee3c1c39869fb0ca52eb7b9c9ef7c410b3fe9b0b8530ac2b4cab6ccb8",
        "bytes": 301399
      }
    ],
    "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": "Preserve the evidence separating connector filtering from the credential boundary.",
      "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": "Experimental status, scope flags and token enforcement guidance."
    },
    "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#doppler-mcp-readonly-token-trust",
  "machine_readable_record": "/varexis-index/records/doppler-mcp-readonly-token-trust.json"
}