{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-22T23:52:06.542Z",
  "record_id": "VXI-EXT-PROCUREMENT-AGENTCORE-DEFAULT-LISTING-TOOL-SCHEMA-SYNC-01-v1",
  "record_kind": "external_reference",
  "title": "AgentCore Gateway: Default listings need explicit refresh after upstream changes",
  "system": "Amazon Web Services",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does AgentCore Gateway automatically reflect independently changed MCP tools in DEFAULT listing mode?",
  "near_questions": [
    "When should AgentCore refresh changed MCP tool schemas?",
    "Can AgentCore DEFAULT mode retain a removed upstream tool definition?",
    "Does an accepted gateway synchronization prove its catalogue is refreshed?",
    "How do AgentCore DEFAULT and DYNAMIC capability listings differ?"
  ],
  "supported_claims": [
    {
      "claim": "DEFAULT listing mode discovers capabilities during target creation or updates and through explicit SynchronizeGatewayTargets calls. AWS directs operators to synchronize after upstream definitions change. Synchronization is asynchronous, so acceptance is not completion. DYNAMIC mode forwards discovery requests and has different documented compatibility limits.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "A guarantee that a particular gateway inventory is stale or that synchronization validates tool behavior",
    "Equivalence between DEFAULT, DYNAMIC and explicitly supplied schema configurations",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "DEFAULT listing mode discovers capabilities during target creation or updates and through explicit SynchronizeGatewayTargets calls. AWS directs operators to synchronize after upstream definitions change. Synchronization is asynchronous, so acceptance is not completion. DYNAMIC mode forwards discovery requests and has different documented compatibility limits.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "MCP servers targets",
    "source_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-MCPservers.html",
    "checked_on": "2026-10-22",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-AGENTCORE-DEFAULT-LISTING-TOOL-SCHEMA-SYNC-01-v1",
    "candidate_record_sha256": "3039fd120f3a5f2030b7c3da2a9dc6797cb57f9e4e2e66b3a35c970c44625989",
    "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": "DEFAULT listing mode discovers capabilities during target creation or updates and through explicit SynchronizeGatewayTargets calls. AWS directs operators to synchronize after upstream definitions change. Synchronization is asynchronous, so acceptance is not completion. DYNAMIC mode forwards discovery requests and has different documented compatibility limits.",
    "required_buyer_context": "Target listing mode and any explicitly supplied schema; Upstream definition revision and gateway inventory revision; Synchronization request identity and completed target status. Buyer deployment not inspected.",
    "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.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-22",
    "claim_to_check": "Does AgentCore Gateway automatically reflect independently changed MCP tools in DEFAULT listing mode?",
    "documented_statement": {
      "status": "documented",
      "statement": "DEFAULT listing mode discovers capabilities during target creation or updates and through explicit SynchronizeGatewayTargets calls. AWS directs operators to synchronize after upstream definitions change. Synchronization is asynchronous, so acceptance is not completion. DYNAMIC mode forwards discovery requests and has different documented compatibility limits.",
      "source_ids": [
        "agentcore-targets"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "A current inventory claim needs the listing mode and completed synchronization evidence.",
      "source_ids": [
        "agentcore-targets"
      ]
    },
    "buyer_evidence_required": [
      "Target listing mode and any explicitly supplied schema",
      "Upstream definition revision and gateway inventory revision",
      "Synchronization request identity and completed target status"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse a current-schema claim based solely on target creation history or synchronization acceptance."
    },
    "unknowns": "The buyer upstream changes, configured listing mode and latest completed synchronization are unobserved.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer upstream changes, configured listing mode and latest completed synchronization are unobserved."
    },
    "evidence_sources": [
      {
        "source_id": "agentcore-targets",
        "url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-MCPservers.html",
        "final_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-MCPservers.html",
        "title": "MCP servers targets",
        "checked_on": "2026-10-22",
        "captured_at_utc": "2026-10-22T23:48:43.306Z",
        "version_context": "Rolling AgentCore Gateway guide; DEFAULT and DYNAMIC listing modes must be distinguished.",
        "sha256": "d488b948fa4a5260f04b1d41ab13cf7db153fc11230abb0783b80394c226d63a",
        "bytes": 33437,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Listing Mode",
          "Implicit Synchronization",
          "Explicit Synchronization",
          "When to call SynchronizeGatewayTargets"
        ],
        "capture_status": 200,
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Avoid approving tools against an outdated definition or incomplete refresh.",
      "free": "Complete review, sources, practical questions 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": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Avoid approving tools against an outdated definition or incomplete refresh.",
    "refusal_conditions": [
      "Refuse a current-schema claim based solely on target creation history or synchronization acceptance."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Avoid approving tools against an outdated definition or incomplete refresh.",
    "comparison_role": "supplementary_discovery"
  },
  "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#agentcore-default-listing-tool-schema-sync",
  "machine_readable_record": "/varexis-index/records/agentcore-default-listing-tool-schema-sync.json"
}
