Threat explainer
Workspace trust boundaries
How AI agents cross workspace boundaries — reading other projects, team configs, and monorepo secrets.
- 01
AI tools can see files outside your project. That can leak data across teams.
- 02
Workspace trust boundary violations occur when an agent reads files from adjacent projects, shared monorepo configs, or team-wide credentials that fall outside its intended task scope.
- 03
HOL Guard turns these moments into private receipts first, then public lessons only after redaction and moderation.
Harness setup guides
Protect the coding tools your team already uses without forcing everyone to become a security expert.
Codex
Terminal-native coding agent with broad shell reach.
Open guideharnessClaude Code
Agentic coding harness with MCP and file access.
Open guideharnessGitHub Copilot CLI
IDE and CLI assistant across code and terminal flows.
Open guideharnessCursor
AI-first IDE with repo and terminal context.
Open guideRedacted warnings
Real protection moments, scrubbed for safety before becoming public learning pages.
Codex was stopped before reading an env file
A redacted example of a local secret read attempt.
Why it was risky
Env files often hold API keys or service credentials.
What Guard did
HOL Guard paused the read before file contents left the machine.
Claude Code was stopped before calling an untrusted MCP tool
A redacted example of an MCP tool with a misleading description.
Why it was risky
The tool description asked the agent to read credentials and pass them as arguments.
What Guard did
HOL Guard paused the tool call and flagged the description for review.
Cursor was stopped before following a hidden instruction
A redacted example of a prompt injection via a file comment.
Why it was risky
The instruction was embedded in an HTML comment invisible to the developer.
What Guard did
HOL Guard paused the command and showed the source of the instruction.
OpenCode was stopped before running a malicious postinstall script
A redacted example of a supply-chain attack via npm install.
Why it was risky
Postinstall scripts run with full permissions before anyone reviews the code.
What Guard did
HOL Guard paused the install and showed the script contents.
Safe labs
Practice attack patterns with static simulations. Nothing dangerous executes.