By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Workspace trust and project configuration

A cloned repository can carry agent settings, MCP definitions, hooks and instructions that activate the moment you open it. Trust prompts and restricted modes keep that project configuration inert until a person accepts it. Several 2025 vulnerabilities came from project files that agents loaded, or rewrote, without a trust check.

Read in this order

  1. OfficialVS Code: Workspace TrustStart here: the restricted-mode model that most agents copy.
  2. OfficialGemini CLI: Trusted foldersHow an agent CLI gates project config behind a trusted folder.
  3. OfficialClaude Code security advisoriesReal advisories showing what trust-check gaps looked like in practice.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.