Join our Newsletter — 33% off our NHI Course

Why do Cursor, Codex, Gemini CLI, and Antigravity cross the sandbox boundary?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Trust handoffs let agentic coding tools affect privileged execution even when direct escape is blocked, according to Pillar Security. That makes sandbox rules only as strong as the host components that later trust agent-written files or outputs.

Editorial analysis by NHI Mgmt Group, based on content published by Pillar Security: “The Week of Sandbox Escapes”.

Key questions

Q: Why do agentic coding tools create a different risk profile from standard developer tools?

A: They collapse reading, reasoning, and execution into one workflow.

Q: What are the signs that sandbox containment is failing in practice?

A: Look for agent workflows that depend on path-based trust, parent-written outputs, or allow lists that hide risky destinations behind normal-looking operations.

Q: What breaks when an agentic coding tool sandbox is not enough?

A: The sandbox breaks when the agent can write something that another trusted component later runs or trusts.

Practitioner guidance

  • Define trust-handoff boundaries for agentic endpoints Map every place an agent can write, every host component that can read those writes, and every path that turns a file into execution.
  • Classify workspace artefacts as executable risk Review hooks, task files, virtualenv interpreters, Git metadata, and IDE configs as potential execution inputs rather than inert project state.
  • Enforce invocation-level command policy Move beyond command-name allowlists and inspect the full invocation, arguments, directory context, and side effects before execution.

Bottom line: Agentic coding tools can remain inside a sandbox and still create risk if host components later trust what they wrote.

Glossary terms: Trust Handoff, Sandbox Boundary, Executable Workspace State, Agentic Endpoint Security

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Trust handoff governance is the missing control plane for agentic coding tools. The article shows that the meaningful boundary is not the model process but the seam between agent output and host execution. When a privileged helper, extension, or daemon consumes agent-written content, the risk becomes a governance problem over who trusts what, when, and under which provenance rules. Practitioners should treat that seam as a control objective, not an implementation detail.

A few things that frame the scale:

  • Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
  • 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.

A question worth separating out:

Q: Should security teams treat agentic coding tools as endpoint actors or ordinary developer tools?

A: They should treat them as endpoint actors because they can influence host behaviour, not just produce text. Once a tool can write files that trusted components execute, it participates in endpoint control flow and needs monitoring, policy enforcement, and provenance tracking like any other actor with delegated authority.

👉 Read our full editorial: Agentic coding tools need a sandbox model built for trust handoffs



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.