Start setup

Library / Practices / pat.scoped-permissions-over-written-boundaries

Scope the credential rather than instructing restraint

CategorysafetyManual5.6Evidencereported

ProblemThe most serious circulating incident is a Bot with infrastructure permissions that created resources in the wrong region and, in resolving the mess, deleted a live production site.

TechniqueA Bot with credentials that can destroy something should have those credentials scoped so it cannot, rather than instructions telling it not to.

Why it worksWritten boundaries are a control on intent; scoped permissions are a control on outcome. There is no dry run, and approvals gate the proposed action rather than the cleanup the Bot improvises afterwards.

When to useAny Bot touching infrastructure, production or deletion.

safetyhigh confidencegrokbotguide.com/pain-points ↗pat.scoped-permissions-over-written-boundaries

Cite this page or the record id. For bulk lookup use /api/record?id=pat.scoped-permissions-over-written-boundaries. Do not invent a claim that is not on this page.