{ "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-14T00:29:51.399Z", "record_id": "VXI-EXT-TOOL-TRUST-SNYK-01-v1", "record_kind": "external_reference", "title": "Snyk MCP: Folder trust and scan-time build execution", "system": "Snyk MCP", "evidence_family": "agent_tool_trust_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Can a Snyk dependency scan execute project tooling, even when the task is only a security review?", "near_questions": [ "Can a Snyk dependency scan run build tools?", "Does a security scan always avoid local code execution?", "What does Snyk folder trust establish?", "Which Snyk organization receives a scan?", "Can an MCP scan trigger authentication?", "What should I review before scanning an unfamiliar repository?", "Does a clean Snyk result establish deployment safety?", "Which project data leaves the local scan environment?", "Can an installed Snyk tool be skipped by an agent?", "What evidence supports permission to run dependency tooling?", "Can I retain the Snyk scan-execution boundary?", "When should an agent stop before scanning untrusted project code?" ], "supported_claims": [ { "claim": "Snyk documents that dependency scanning can invoke ecosystem tools such as build systems to obtain a dependency tree. The MCP integration includes folder-trust and authentication controls. Review the repository and execution context before scanning; a scan request is not proof that untrusted project tooling is safe to run.", "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": "Snyk documents that dependency scanning can invoke ecosystem tools such as build systems to obtain a dependency tree. The MCP integration includes folder-trust and authentication controls. Review the repository and execution context before scanning; a scan request is not proof that untrusted project tooling is safe to run.", "related_record_ids": [ "VXI-EXT-TOOL-TRUST-BROWSERBASE-01-v1", "VXI-EXT-TOOL-TRUST-N8N-01-v1", "VXI-EXT-TOOL-TRUST-SEMGREP-GUARDIAN-01-v1", "VXI-EXT-TOOL-TRUST-PAGERDUTY-01-v1" ], "source_review": { "source_type": "official_external_documentation", "source_title": "Snyk MCP scanning, folder trust and ecosystem execution", "source_url": "https://github.com/snyk/studio-mcp", "checked_on": "2026-10-14", "candidate_record_id": "VXI-EXT-TOOL-TRUST-SNYK-01-v1", "candidate_record_sha256": "a469a68467f50d85c38edcec35e0f8cea4adf161c0ec84def0dfd1232baae391", "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": "Snyk documents that dependency scanning can invoke ecosystem tools such as build systems to obtain a dependency tree. The MCP integration includes folder-trust and authentication controls. Review the repository and execution context before scanning; a scan request is not proof that untrusted project tooling is safe to run.", "required_buyer_context": "Repository trust, scan type, ecosystem, CLI identity, organization and permitted local execution.", "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": "Snyk MCP", "variant": "Official Studio MCP and CLI-backed scanning" }, "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": "Snyk publishes Studio MCP and the supporting CLI.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "purpose", "label": "Purpose", "status": "documented", "statement": "Scan code, dependencies, configuration and other supported artifact types.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "reads", "label": "Read capability", "status": "documented", "statement": "Selected project contents, dependency information and scan results.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "writes", "label": "Write capability", "status": "documented", "statement": "Dependency scans may invoke third-party ecosystem tooling locally.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "auth", "label": "Authentication", "status": "documented", "statement": "CLI authentication supports OAuth and other documented token methods.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "permissions", "label": "Permission surface", "status": "documented", "statement": "Folder trust, selected scan and authenticated organization affect operation.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "egress", "label": "Data leaving the environment", "status": "review_inference", "statement": "Assess project information sent to Snyk and local tools for the chosen scan.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "failures", "label": "Failure modes to consider", "status": "review_inference", "statement": "Untrusted build tooling or the wrong organization can invalidate the intended scan boundary.", "source_ids": [ "snyk-main", "snyk-auth" ] }, { "field": "unknown", "label": "Unknowns and applicability", "status": "unknown", "statement": "Repository behavior, effective trust settings and scan-product data flow are unverified.", "source_ids": [] }, { "field": "gate", "label": "Suggested refusal or clarification condition", "status": "varexis_review_policy", "statement": "Require repository and execution-scope review before scans that invoke project tooling.", "source_ids": [] } ], "evidence_sources": [ { "source_id": "snyk-main", "url": "https://github.com/snyk/studio-mcp", "final_url": "https://github.com/snyk/studio-mcp", "title": "Snyk MCP scanning, folder trust and ecosystem execution", "checked_on": "2026-10-14", "sha256": "9232ecc44c18efcbd13b743e059fc3877a0270682fedd9c5efa01e6928810e99", "bytes": 276889 }, { "source_id": "snyk-auth", "url": "https://docs.snyk.io/developer-tools/snyk-cli/authenticate-to-use-the-cli", "final_url": "https://docs.snyk.io/developer-tools/snyk-cli/authenticate-to-use-the-cli", "title": "Snyk CLI authentication and account selection", "checked_on": "2026-10-14", "sha256": "d5ff4ada5324a6f2d616d4c34b6d635df914b888d744ae0dcb1017560aec9195", "bytes": 718966 } ], "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 the folder-trust and execution-context assumptions attached to a scan approval.", "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": "Recheck scan type, build-tool behavior, folder trust and Snyk organization." }, "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#snyk-mcp-folder-scan-execution-trust", "machine_readable_record": "/varexis-index/records/snyk-mcp-folder-scan-execution-trust.json" }