{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-23T02:13:06.885Z",
  "record_id": "VXI-EXT-PROCUREMENT-AGENTCORE-POLICY-SHADOW-MODE-ACTIVATION-01-v1",
  "record_kind": "external_reference",
  "title": "AgentCore Policy: Active rules still depend on gateway enforcement mode",
  "system": "Amazon Web Services",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an ACTIVE AgentCore policy enforce its decision when the gateway is in LOG_ONLY mode?",
  "near_questions": [
    "Can an ACTIVE AgentCore policy still be observation only?",
    "Which AgentCore setting wins between engine LOG_ONLY and policy ACTIVE?",
    "Does an AgentCore deny trace prove that a tool call was blocked?",
    "How do per-policy shadow tests differ from gateway enforcement mode?"
  ],
  "supported_claims": [
    {
      "claim": "AgentCore separates gateway policy-engine mode from each policy's enforcement mode. Gateway LOG_ONLY records decisions without enforcing any policy, including ACTIVE policies. With gateway ENFORCE, ACTIVE policies contribute to the enforced decision while individual LOG_ONLY policies are evaluated separately. Both settings must be checked; a policy status or denial trace alone does not establish blocking.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Proof that a particular request was blocked or that every MCP method is covered",
    "A claim that LOG_ONLY disables gateway authentication or all other access controls",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "AgentCore separates gateway policy-engine mode from each policy's enforcement mode. Gateway LOG_ONLY records decisions without enforcing any policy, including ACTIVE policies. With gateway ENFORCE, ACTIVE policies contribute to the enforced decision while individual LOG_ONLY policies are evaluated separately. Both settings must be checked; a policy status or denial trace alone does not establish blocking.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Test a policy in LOG_ONLY mode",
    "source_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-test-a-policy.html",
    "checked_on": "2026-10-23",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-AGENTCORE-POLICY-SHADOW-MODE-ACTIVATION-01-v1",
    "candidate_record_sha256": "bea937954c5de527047467cb84849cf2c4b6123f0800b32627ab147310a85731",
    "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": "AgentCore separates gateway policy-engine mode from each policy's enforcement mode. Gateway LOG_ONLY records decisions without enforcing any policy, including ACTIVE policies. With gateway ENFORCE, ACTIVE policies contribute to the enforced decision while individual LOG_ONLY policies are evaluated separately. Both settings must be checked; a policy status or denial trace alone does not establish blocking.",
    "required_buyer_context": "Gateway policyEngineConfiguration mode and attached engine identity; Individual policy enforcementMode and applicable policy definitions; Dated invocation, effective decision and downstream outcome evidence. 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-23",
    "claim_to_check": "Does an ACTIVE AgentCore policy enforce its decision when the gateway is in LOG_ONLY mode?",
    "documented_statement": {
      "status": "documented",
      "statement": "AgentCore separates gateway policy-engine mode from each policy's enforcement mode. Gateway LOG_ONLY records decisions without enforcing any policy, including ACTIVE policies. With gateway ENFORCE, ACTIVE policies contribute to the enforced decision while individual LOG_ONLY policies are evaluated separately. Both settings must be checked; a policy status or denial trace alone does not establish blocking.",
      "source_ids": [
        "agentcore-policy-modes"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Review evidence should bind both mode settings to the invocation period before relying on a claimed policy denial.",
      "source_ids": [
        "agentcore-policy-modes"
      ]
    },
    "buyer_evidence_required": [
      "Gateway policyEngineConfiguration mode and attached engine identity",
      "Individual policy enforcementMode and applicable policy definitions",
      "Dated invocation, effective decision and downstream outcome evidence"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse an enforced-denial claim based only on an ACTIVE policy label or a LOG_ONLY decision trace."
    },
    "unknowns": "The buyer gateway settings, applicable policies, other controls and actual request outcome are unobserved.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer gateway settings, applicable policies, other controls and actual request outcome are unobserved."
    },
    "evidence_sources": [
      {
        "source_id": "agentcore-policy-modes",
        "url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-test-a-policy.html",
        "final_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/policy-test-a-policy.html",
        "title": "Test a policy in LOG_ONLY mode",
        "checked_on": "2026-10-23",
        "captured_at_utc": "2026-10-23T02:08:12.209Z",
        "version_context": "Rolling AgentCore Policy developer guide captured on the review date; policy-level ACTIVE/LOG_ONLY and gateway-level ENFORCE/LOG_ONLY are separate controls.",
        "sha256": "6a90db23d9c9e9b6e5791609e8c85d0725757d92aa5fe2b504d114269fbd4c6d",
        "bytes": 48104,
        "capture_status": 200,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "How LOG_ONLY mode works",
          "LOG_ONLY policies and LOG_ONLY policy engines"
        ],
        "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 a deployment whose expected permission rules are only being observed rather than applied.",
      "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 a deployment whose expected permission rules are only being observed rather than applied.",
    "refusal_conditions": [
      "Refuse an enforced-denial claim based only on an ACTIVE policy label or a LOG_ONLY decision trace."
    ]
  },
  "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 a deployment whose expected permission rules are only being observed rather than applied.",
    "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-policy-shadow-mode-activation",
  "machine_readable_record": "/varexis-index/records/agentcore-policy-shadow-mode-activation.json"
}
